Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to Push Large Docker Images to Harbor installed in an RKE2 Cluster #19323

Closed
aboualiaa opened this issue Sep 7, 2023 · 2 comments
Closed

Comments

@aboualiaa
Copy link

aboualiaa commented Sep 7, 2023

Setup:

  • RKE2 cluster managed with Rancher.
  • ceph-csi as a CSI driver installed via Helm.
  • Functioning Harbor installation (Version 2.9.0) also set up via Helm
  • Persistent Volume Claims (PVCs) provided by ceph's csi-cephfs.

Objective:
I'm attempting to push large Docker images (e.g., freesurfer/freesurfer:7.2.0, which is almost 5 Gb) to Harbor. While pushing small images works seamlessly, I encounter difficulties with large images.

Attempts Made:

  1. Increased the size of PVCs within the Kubernetes cluster (e.g. for the registry to 50 Gb, all other PVCs to 15 Gb)

  2. Attempted pushing using both Docker and Podman; both retried several times before failing.

  3. The only error message that could be useful I received from Skopeo:

    Error copying ref "docker://freesurfer/freesurfer:7.2.0": writing blob: Patch "https://my.local.harbor/v2/library/freesurfer/blobs/uploads/d19338fa-c32f-4cdc-8716-efdd84e0d19e?_state=3TqbKhk0jzmA5dmrhNWyb-aEdvTHOnBlSxWJOmTUEdp7Ik5hbWUiOiJsaWJyYXJ5L2ZyZWVzdXJmZXIiLCJVVUlEIjoiZDE5MzM4ZmEtYzMyZi00Y2RjLTg3MTYtZWZkZDg0ZTBkMTllIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDIzLTA5LTA3VDA4OjU0OjE4LjA0NTA4MTA2MloifQ%3D%3D": EOF
    

Any insights or guidance on this issue would be greatly appreciated, the Harbor installation is for my use case unusable because of this.

Am I missing something? Is there an image size limit? An upload timeout?

@stonezdj
Copy link
Contributor

stonezdj commented Sep 7, 2023

It maybe related to the network timeout, because I can upload the same image to Harbor installed with docker-compose.
see issue: #17908 or #15751. you should check the timeout setting in the LB/Ingress etc.

@aboualiaa
Copy link
Author

aboualiaa commented Sep 7, 2023

Thank you! It was the timeouts from the load balancer (haproxy) in front of the kubernetes cluster. Closing as solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants