#Error pulling from private registry
wary willow
I'm using the python SDK
barren schooner
Ooh sorry, I misread
wary willow
no problem 🙂
btw I'm really struggling with private repos, is this supposed to be easier? I had to also setup two _EXPERIMENTAL env variables
regarding the problem, do you know if there is some argument that I can provide to dagger/engine when docker running it?
barren schooner
Can you please list all the steps you followed please ?
barren schooner
btw I'm really struggling with private repos, is this supposed to be easier? I h...
Why did you have to set up the _EXPERIMENTAL env vars ?
cc @exotic kettle
wary willow
- echo "_EXPERIMENTAL_DAGGER_RUNNER_HOST=${{ env.DAGGER_HOST }}" >> $GITHUB_ENV
- echo "_EXPERIMENTAL_DAGGER_CLI_BIN=$(pwd)/${{ env.DAGGER_CLI_BIN }}" >> $GITHUB_ENV
since otherwise the dagger example script.py would try to download stuff from dl.dagger.io
but it is behind a firewall, so I cannot access it
barren schooner
You're right, I recall now 😇
wary willow
but then, why dagger-cue it's working in the first place? 🤔
barren schooner
but then, why dagger-cue it's working in the first place? 🤔
I believe that you're actually not using the same engine here
Did you set BUILDKIT_CA_CERTS inside your buildkit container ? https://github.com/dagger/dagger/issues/2016
exotic kettle
@wary willow are the certificates of your registry self signed?
wary willow
Did you set `BUILDKIT_CA_CERTS` inside your buildkit container ? https://github....
I have to check this
but I know for sure that private images sent to this instance can be built
from what I'm seeing, this is the only extra added to buildkit run: --addr unix:///run/buildkit/buildkitd.sock --addr tcp://0.0.0.0:1347 --debug
no extra env vars
exotic kettle
Can you jump in a video call to share?
wary willow
Sorry, I was ahead of myself. I talked with a colleague, and we have to first discuss it internally before calling you guys
However, thank you for your helpfulness 🙂
I will also try to look into buildkit certs
barren schooner
In theory, I presume that the way to make it work is to copy, inside the dagger-engine container, the corresponding certificates: -v $PWD/my-cert.pem:/etc/ssl/certs/my-cert.pem
The fact that it works on dagger-cue and not on the SDK is what seems weird
oak terrace
Hey @wary willow -- we've added this document a few days ago: https://github.com/dagger/dagger/blob/main/core/docs/d7yxc-operator_manual.md#configuration
I think that should cover this use case /cc @fallen cedar
fallen cedar
Yes that's currently the route to solve this, but we realize it's pretty far from ideal. There is another proposal here on what may be a much easier-to-use solution: https://github.com/dagger/dagger/issues/4217
