https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
f
Deleted; was responding in the wrong thread
Deleted
I would first try if the issue can be reproduced by pushing to Docker Hub or the GitHub container registry.
Also maybe try upgrading to a later version of Rancher Desktop, and/or try switching from QEMU to VZ or vice versa to see if that makes a difference
r
Thanks @fast-garage-66093! • Upgraded to latest Rancher version (no success). • Switched container engine (from dockerd to containerd) --> same I noticed the following errors in the logs during the push but somehow the CLI doesn't complain about a 401 (I also logged successfully to the private registry). Not sure if this would cause the EOF I am observing..
Copy code
level=debug msg=Unauthorized digest="sha256:6c03c4b4a6e0c8c4db9a1f4e93569fa408cb8e859862be1f790bb8732d1f3c5b"
Found an interesting JIRA about this scenario: • A token is created during a blob push. • The token might expire and lead to a 401. • I am seeing the EOF exactly 62sec after starting the push command and usually it fails when sending the large blob (1.6GB) since all the other ones have been processed. https://github.com/docker/hub-feedback/issues/1944
f
Yeah, that is indeed interesting. Which is why it would be helpful to know if the problem can be reproduced using Docker Hub or GitHub.
I know there are some network issues with large container images when using VZ mode, which is why I suggested using QEMU, to see if it makes a difference.
Another thing to check: are you using the "allowed images" features? Because that goes through a proxy that could introduce problems as well.
r
Thanks @fast-garage-66093! Yes, I am using the "allowed images" feature as I am targeting a private registry: phx.ocir.io. Can I push my image with setting the allowed images?
@fast-garage-66093 • I disabled the "allowed images" feature since I am loging in to the registry. • The EOF issue is gone. • Now my large image is getting uploaded though slowly. I will update you on the operation status; thank you so much for your help!!!
f
The "allowed images" feature is not necessary to access a private registry. It is used to avoid accidentally pulling images from non-approved locations (e.g. by just using a Helm chart without first verifying all the images names).
👍 1
Could you create a GitHub issue for this?
👍 1
r
Image (1.7 GB) uploaded successfully after disabling the experimental feature; now creating the JIRA. Thanks @fast-garage-66093 for your help!
f
You are welcome! And by JIRA I hope you mean a GitHub issue 😄
r
Yes.. apologies just used to the "JIRA" terminology within my team 🙂
6 Views
Open in Slack
PreviousNext
Powered by