From @rdnt
I think I found a bug in bob
- Trying to build bobc, the bobfile is three or so tasks, one creates a docker container
- I build it once and push the images to the remote store.
- I do bob clean system and docker system prune -a -f to purge all images
- If I try to do bob build container, the images are successfully pulled, but then I get this error:
?:~/projects/benchkram/bob-server/core$ bob build container
Using 24 workers
Running task container with 3 dependencies
generate-go-api pulling artifact 100% (5.9kB/5.9kB)
server pulling artifact 25% (3.0MB/12MB)
server pulling artifact 92% (11MB/12MB)
server pulling artifact 100% (12MB/12MB)
build pulling artifact 98% (12MB/12MB)
build pulling artifact 100% (12MB/12MB)
container pulling artifact 16% (12MB/72MB)
container pulling artifact 33% (24MB/72MB)
container pulling artifact 50% (36MB/72MB)
container pulling artifact 67% (48MB/72MB)
container pulling artifact 84% (61MB/72MB)
container pulling artifact 100% (72MB/72MB)
● ● ● ●
Ran 4 tasks in 11.4s
generate-go-api cached (401.4ms)
server cached (2.5s)
build cached (1.4s)
container failed (7.2s)
Failed to fetch docker image hash: bobc:latest, image not found
- At this point the image is already there on the local docker image store docker images ls -a
- If I try to do bob build container afterwards it succeeds.
My assumption is that the image does not become immediately available to the docker daemon, so when we try to use it we get the error.
From @rdnt
I think I found a bug in bob
My assumption is that the image does not become immediately available to the docker daemon, so when we try to use it we get the error.