So strange issue. When using buildx, pants docker target fails to correctly parse and insert dependency images when a "Setup buildx" action is run on gitlab CI. It fails to correctly reference the image it built for a base image. It seems to insert an extra ":" at the end of the image name. After removing the "Set up Docker Buildx", it works. I'm using the system for referencing targets similar to here: https://www.pantsbuild.org/stable/docs/docker#dependency-inference-support I'm using a similar packaging system as referenced here: https://www.pantsbuild.org/blog/2022/08/02/optimizing-python-docker-deploys-using-pants#multiple-images-and-tagging CI failure: https://github.com/Benjamin-Etheredge/mono/actions/runs/13358078904/job/37303585606 This isn't a big issue, but it could be evidence of incompatibility with something in buildx. Or it could also be some PATH stuff is getting polluted when buildx setup action runs, and it's user error. I just wanted to let yall know it was a thing just in case.

Thanks for the info! I’ll let someone with more docker backend experience weigh in on what we should do about this…

I've had a possibly similar experience (with GitHub), will try to give you some hints hoping it helps. First of all, make sure that buildx is working with the "docker" backend. Also, make sure the containerd store image is effectively used.