Bug #3457


docker-playground: repository 'laforge/debian-jessie-build' not found

Added by fixeria over 5 years ago. Updated over 5 years ago.

Target version:
Start date:
Due date:
% Done:


Spec Reference:


There is a problem appearing when building Docker images based on 'laforge/debian-jessie-build'...

After building, the 'debian-jessie-build' image is being tagged according to the following rule:

$(USER)/$(IMAGE) # e.g. user/debian-jessie-build

so, if the current $(USER) != 'laforge', build fails:

make[1]: Leaving directory `/home/user/osmocom/docker-playground/debian-jessie-build'
make -C osmo-stp-master
make[1]: Entering directory `/home/user/osmocom/docker-playground/osmo-stp-master'
docker build --build-arg USER=user -t .
Sending build context to Docker daemon  9.216kB
Step 1/16 : FROM laforge/debian-jessie-build
repository laforge/debian-jessie-build not found: does not exist or no pull access
make[1]: *** [docker-build] Error 1
make[1]: Leaving directory `/home/user/osmocom/docker-playground/osmo-stp-master'
make: *** [osmo-stp-master] Error 2

because there is no 'laforge/debian-jessie-build', there are:

# docker image ls
REPOSITORY                TAG                 IMAGE ID            CREATED             SIZE
user/debian-jessie-build  latest              1f6421af8bfc        15 minutes ago      621MB
debian                    jessie              79f4bda91989        3 weeks ago         127MB

I started to think, may we parametrize the 'FROM laforge/debian-jessie-build' somehow?
Fortunately, yes! The following header makes the trick:

FROM    $USER/debian-jessie-build

A change will be sent soon...

Actions #1

Updated by fixeria over 5 years ago

It should have been noted that I didn't experience this problem previously, most likely because
the 'debian-jessie-build' was tagged as 'laforge/debian-jessie-build', so after removing all
images I had and rebuilding from the recent Dockerfile, I have got '$USER/debian-jessie-build'.

Actions #2

Updated by osmith over 5 years ago

  • Assignee changed from fixeria to osmith

I'll try to confirm that the fix works, and then submit a patch.

Actions #3

Updated by osmith over 5 years ago

Works for me (after upgrading to docker-ce), patch submitted:

laforge mentioned, that Jenkins runs docker-ce as well, so this should not be a problem.

Actions #4

Updated by osmith over 5 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 90
Actions #5

Updated by osmith over 5 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

patch has been merged


Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)