Docker cache untagging images between pipelines

[tom.noble]

I'm currently trying to use docker and docker-compose to run some tests in parallel via a bitbucket pipeline. Since the services running the tests are all based off the same image, I'm attempting to build it once in a separate pipeline, cache the results, then use the image when calling docker-compose up in the other pipeline -- saving some time when actually running the tests.

The the image below shows the docker image being built and cached as expected in the first pipeline

However, when attempting to use the image in the second, I get the following error. Listing the images present on that pipeline shows that, although the correct image seems to be getting cached and fetched (same image ID), the tag is now missing.

I'm unsure if this is an issue on bitbucket's end, or whether I'm using this functionality incorrectly... Any help would be appreciated!

[Daniil Penkin]

Hello @tom.noble ,

Welcome to the Community!

The cache is not meant to be used for consuming images like this. All caches (not just Docker) are in place to speed up build process, when possible. Note that they are not updated on every build, and your build should be prepared for caches to be absent at any time.

What you need to do is to push your docker image to some Docker registry (like Docker Hub, AWS or self-hosted) and then pull it from there.

Hope this helps. Let me know if you have any questions.

Cheers,
Daniil