Actions
Bug #3457
closeddocker-playground: repository 'laforge/debian-jessie-build' not found
Start date:
08/09/2018
Due date:
% Done:
100%
Spec Reference:
Description
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 docker.io/user/osmo-stp-master:latest . 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:
ARG USER FROM $USER/debian-jessie-build
A change will be sent soon...
Actions