registry TLS error

[lone plaza]

Hi, is your computer behind a corporate proxy?
Is it your first time using dagger?

[frosty hearth]

yes first time using dagger and yes it is behind a corporate proxy and the proxy is set in Docker Desktop correctly.

[lone plaza]

if you do:

docker run -it ubuntu bash

And then, inside this shell, install curl

apt install curl -y

And then, do a

curl -v https://registry-1.docker.io/v2/

And then, paste me the output?

[frosty hearth]

@lone plaza - I could get past the error by customizing the build kit using this instruction - https://docs.dagger.io/1223/custom-buildkit/.
My main.cue looks like this
...
dagger.#Plan & { actions: { _alpine: core.#Pull & {source: "<my_internal_registry>/alpine:3"}
...
It seems like it fails when trying to pull from my internal registry. Is there a way to tell dagger to not use Docker Hub Registry?

[lone plaza]

It also fails when pulling from your internal registry?

With the same error message?

[frosty hearth]

The error is FTL failed to execute plan: task failed: actions._alpine: <internal_registry>/alpine:3: not found

I could pull the same image by doing docker pull <internal_registry>/alpine:3

[lone plaza]

Ok, so I guess what's missing is the auth part from your docker.#Pull

[lone plaza]

can you try that?

// … (package, imports)
 
dagger.#Plan & {
    client: env: {
        USERNAME: string
        SECRET:   dagger.#Secret
    }

    actions: {
        _pull: docker.#Pull & {
            source: "<my-private-registry>/alpine:3"
            auth: {
                username: client.env.USERNAME
                secret:   client.env.SECRET
            }
        }
        // reference _pull.output as the input for the action you want to run
        }
}