I’m trying to push to a repo hosted with a self signed certificate. How would I trust the certificate in the bluebuild cli so that the container can access that repo?

message has been deleted

I think that would have to be a setting you would change for

podman

or

docker

Okay so I wanted to be able to trust the repo instead of pushing insecure. Im able to trust the repo in the workflow container, but bluebuild seems to build the image and not use the system certs to push. In the workflow container I can verify the cert but the bluebuild cli won’t accept it. I also tried using the archive option but there must be a —push option hardcoded into the bluebuild cli prebuilt container because it gives me the “can’t archive with push enabled” error even with BUILD_AND_PUSH=false. I’m not sure where bluebuild is saving the built images, but I can’t find them anywhere on the workflow container so I can’t manually push them either.

Ah so the Github Action uses

docker buildx

so it spins up a buildkit container that does the actual image building. It should be labeled as

bluebuild

when you run

docker buildx ls

. I'm not sure what you'll need to do for that, but that should help point you in the right direction

So I managed to get the build working by manually creating an archive with

docker buildx build

and then using skopeo to copy it to remote since those programs seem to listen to the system certificates

We use

earthly

for our builds. I have to work on migrating to

earthbuild

though since that's the maintained fork

Thanks for this! I’ll try to get it working with this.

The

update-ca-trust

should be on the next line as a separate command