compose: `docker-compose bundle` failed with ERROR: Some images are missing digests.
I would like to convert a simple compose k8s guestbook below to bundle format.
version: "2"
services:
redis-master:
image: gcr.io/google_containers/redis:e2e
ports:
- "6379"
redis-slave:
image: gcr.io/google_samples/gb-redisslave:v1
ports:
- "6379"
environment:
- GET_HOSTS_FROM=dns
frontend:
image: gcr.io/google-samples/gb-frontend:v4
ports:
- "80:80"
environment:
- GET_HOSTS_FROM=dns
I tried docker-compose up -d
first without issue. By running that command, docker would pulled the images.
$ docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
gcr.io/google-samples/gb-frontend v4 e2b3e8542af7 4 months ago 512.2 MB
gcr.io/google_samples/gb-redisslave v1 5f026ddffa27 13 months ago 109.5 MB
gcr.io/google_containers/redis e2e e5e67996c442 17 months ago 419 MB
However then using docker-compose bundle
getting error like this:
$ docker-compose bundle --out guestbook.dsb
ERROR: Some images are missing digests.
The following images need to be pulled:
gcr.io/google-samples/gb-frontend:v4
gcr.io/google_containers/redis:e2e
gcr.io/google_samples/gb-redisslave:v1
Use `docker-compose pull gcr.io/google-samples/gb-frontend:v4 gcr.io/google_containers/redis:e2e gcr.io/google_samples/gb-redisslave:v1` to pull them.
Any suggest ?
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Reactions: 3
- Comments: 15
Same problem here with local images š¦
Note: I pulled with
docker-compose pull
but doesnāt work.Ah, yes, I love when issues arenāt fixed but closed anyway.
The image digest is only available if you push the image to a repository. The local build has a container hash (the image ID) but by some technical reason this is not the same digest the bundle needs.
This bug should have been closed long ago since it is not a bug and people misunderstand with good reasons the subtle difference between image digest (available from a repository) and image id. Me included.
The unhelpful
Use `docker-compose push example-service:v1` to push them.
line should be removed due to two main reasons: 1) it is wrong and as illustrated by the comments 2) people need to be aware of how they spawned docker-compose (with -f or environment variables) to push the images to the correct repository.Reference: https://github.com/moby/moby/issues/32016
Ping @shin-
Frustrating š Is this a bug not fixed sins 2016 or are we doing something wrong here?
When I donāt create a bundle it works
Try docker-compose pull <Image names>
I also encountered this problem. Is there any way I can bundle the ādockersā created locally(never pushed to dockerhub)?.
same here
I get the same problem with an image Iāve built locally:
Even images pulled, the issue still happened again and again. I guess there is problem with image digest.