-
Notifications
You must be signed in to change notification settings - Fork 510
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
Buildx is not honouring the insecure registry config in toml config provided by the default builder. #777
Comments
My setup on gitlab CI
On
|
Seems to work for me
in logs I see
So it is going to port 80 |
Why are you setting a mirror to the same name as your server? |
oh, because i hosted gitlab myself, so it return back to gitlab local registry. As gitlab.com got connection issue last few days |
This doesn't make any sense. In the worst case, it creates a loop. |
Mirrors part taken from buildkitd.toml.md |
That is an example that fills all field to show them. Mirror is a server that is connected to instead of the registry. If you don't use mirrors then don't set it. |
Oh i see, after looking at my runner log carefully, it pushes image twice. Thanks for the insight, gonna remove it now. |
Specified the config file as:
docker buildx create --name mutli-platform-builder --config /etc/buildkit/buildkitd.toml --driver-opt network=host --use
docker buildx inspect --bootstrap
My sample dockerfile reads like:
When I run the build docker buildx build --platform linux/arm,linux/arm64,linux/amd64 -t 192.168.x.x/docker/muti-arch-test:1.0.0 . --push, error is thrown like error: failed to solve: 192.168.x.x/docker/alpine: failed to do request: Head "https://192.168.x.x/v2/docker/alpine/manifests/latest": dial tcp 192.168.x.x:443: connect: connection refused
From the earlier raised issues, got to know that the global daemon.json insecure registry configuration won't be taken by the builder, and hence I've provided the config and passed to the builder as specified. But still, it is trying to connect to the https port, instead of the http port. Am I doing something wrong here?
The text was updated successfully, but these errors were encountered: