-
Notifications
You must be signed in to change notification settings - Fork 545
Buildx don't push image on private registry #455
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
Comments
You probably used |
@sminodonte did you ever get this sorted ? I have the same issue.. buildx is going directly to DNS and ignore settings in /etc/hosts, one workaround is to specify DNS servers in dockers setting to point to your own and setup A entry for the local registry... which is not a great solution... docker push does not have this issue. |
You can probably customise this by starting up buildkitd container somehow
manually, or patching /etc/hosts in a buildkitd container that buildx
creates. You can also customise it in buildkitd image, if you wish.
…On Tue, 2 Feb 2021, 6:31 pm VladoPortos, ***@***.***> wrote:
@sminodonte <https://github.com/sminodonte> did you ever get this sorted
? I have the same issue.. buildx is going directly to DNS and ignore
settings in /etc/hosts, one workaround is to specify DNS servers in dockers
setting to point to your own and setup A entry for the local registry...
which is not a great solution... docker push does not have this issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#455 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB5MS3LHMCT3IHTLSDA7ZDS5BAGXANCNFSM4UEFLGHA>
.
|
@errordeveloper already sorted, by exactly as you say customizing the build image, I put the steps at the bottom of my web guide for further reference: https://rpi4cluster.com/k3s/k3s-docker-install/ solution by #80 (comment) |
@VladoPortos never sorted...but now I'll try it, thanks @errordeveloper thanks for your solution |
Please resolve this issue. |
I run this command:
docker buildx build --platform linux/arm64 -t IP:_PRIVATE_REGISTRY:5000/i<IMAGE_NAME>:latest . --push
and the result was:
I never had a problem with my private registry about the certificate and I always pushed the image without any problem.
It happened with make a build with buildx
do you have any idea?
Thanks
The text was updated successfully, but these errors were encountered: