#using docker insecure registry
1 messages Β· Page 1 of 1 (latest)
Hello! Are you getting an error when publishing to an insecure registry? We have a few internal test cases that I believe publish to an http-only registry running on localhost, so I'm curious if you are running in a different circumstance and seeing some different behavior
I have this error: failed to solve: failed to do request: Head "https://10.3.4.18:5000/v2/mic-greeting/blobs/sha256:c74e0de79d1e9a8043ef662aff07d982ffa52ccd7627779d19b4f455e7d04f39": http: server gave HTTP response to HTTPS client. My test registry (10.3.4.18:5000) is on the local network and is an http one.
Cool, it seems like that error only happens on non-localhost addresses, I could reproduce it now. I gave a quick shot at fixing it but it wasn't working for me for some reason, so I created an issue for supporting this here: https://github.com/dagger/dagger/issues/4007
User request to be able to push to http registry: #1046817210695417906 message I can confirm that I get the same error but only when tryin...
ok thanks for your quick reply !
Hi! I have the same problem when I want to pull insecure registry. It can be configured? I can't find how
Hey Carlos, on mobile now. Here's a recent conversation I had with a user on how to accomplish this: #1136128194710356038 message.
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
Thanks! I'm using the Python SDK. Can I use the same toml file? I'll try in a while! Thanks again!
Yes, this is an engine configuration. It's independent of the SDK
I'm sorry but I can't do it. I tried with /etc/dagger/engine.toml and not working. I run python ci/main.py build command and see this error:
File "<@beartype(dagger.client.gen.Container.stderr) at 0x7f185b1d9080>", line 10, in stderr
File "/home/calmiron/monorepo/.venv/lib64/python3.11/site-packages/dagger/client/gen.py", line 761, in stderr
return await _ctx.execute(str)
^^^^^^^^^^^^^^^^^^^^^^^
File "/home/calmiron/monorepo/.venv/lib64/python3.11/site-packages/dagger/client/_core.py", line 196, in execute
raise error from e
dagger.QueryError: failed to do request: Head "https://my-registry.local/v2/node/manifests/20.5.0-slim": tls: failed to verify certificate: x509: certificate signed by unknown authority
When add config_path='/etc/dagger/engine.toml' on ci/main.py the error change to:
python ci/main.py build
Error: unknown flag: --project
[...]
File "/home/calmiron/monorepo/.venv/lib64/python3.11/site-packages/dagger/_engine/session.py", line 108, in _get_conn
raise dagger.SessionError(msg)
dagger.SessionError: Failed to start Dagger engine session: Command '/home/calmiron/.cache/dagger/dagger-0.8.1 session --label dagger.io/sdk.name:python --label dagger.io/sdk.version:0.8.1 --project /etc/dagger/engine.toml' returned non-zero exit status 1.
--project is deprecated?
I don't know if I'm very confused. I don't find anything about engine.toml on documentation. :/
# /etc/dagger/engine.toml
debug = true
insecure-entitlements = ["security.insecure"]
[registry."my-registry.local"]
http = true
insecure = true
engine.toml comes from here: https://github.com/dagger/dagger/blob/main/core/docs/d7yxc-operator_manual.md
I mention that in the thread I've shared before here: #1136128194710356038 message. I'm sorry for all the confusion. We're working to improve this experience and document it better π. Happy to jump into a quick #911305510882513037 session tomorrow Carlos to help you with this
Are you speak spanish? π
Genial! π€ Si tenΓ©s unos minutos avisame porfa
@next jungle I have 10 minutes now if you're around
let's go to #911305510882513037
docker run --rm -it \
-v $(pwd)/engine.toml:/etc/dagger/engine.toml \
--privileged \
-p 1234:1234 \
registry.dagger.io/engine:v0.8.1
_EXPERIMENTAL_DAGGER_RUNNER_HOST=docker-container://$container_name
Thanks @dull vault! That's how it works:
# /etc/dagger/engine.toml
# debug = true
insecure-entitlements = ["security.insecure"]
[registry."my-registry.local"]
http = true
docker run --name dagger-engine -v /etc/dagger/engine.toml:/etc/dagger/engine.toml --privileged registry.dagger.io/engine:v0.8.1
export _EXPERIMENTAL_DAGGER_RUNNER_HOST=docker-container://dagger-engine
python ci/main.py build
I am struggling to get insecure working. I have eddited the engine.toml and restarted the dagger engine.
But did you guys have to run the dagger engine container with --priviledged to get it working ?