Hi -
I have a multi-container project I have been working on for many months. Suddenly today, one container no longer builts properly. And the odd thing is that it is showing build commands that aren’t in my Docker.template files.
[xxx] Step 1/13 : FROM resin/raspberrypi3-node:7.8
[xxxx] —> c02233d18507
[xxxx] Step 2/13 : RUN sed -i “s!httpredir.debian.org!curl -s -D - http://httpredir.debian.org/demo/debian/ | awk '/^Link:/ { print $2 }' | sed -e 's@<http://\(.*\)/debian/>;@\1@g'!” /etc/apt/sources.list
[xxxx] Using cache
[xxx] —> a4fed9444ad7
[xxx] Step 3/13 : COPY debian-pinning /etc/apt/preferences.d/
[xxx] lstat debian-pinning: no such file or directory
That base image is not referenced anywhere in my files, and I have no idea where step 2 and 3 come from either.
Is there a rogue build server running?
Thanks
Jay
Did you experience this on multiple builds or just this one?
It would also help a lot if you could show the first few lines of the dockerfile in question and the build output for us to compare…
It was on multiple builds. It seems be related to this line in my Dockerfile.template
FROM resin/raspberrypi3-debian:stretch
WORKDIR /usr/src/app
ENV INITSYSTEM
It was giving a more detailed error message the 2nd day, and I could tell that the 3rd line now needs to be
ENV INITSYSTEM ON
It should have been before, but had been running fine without the “ON” for several months.
Its all set now.
Thanks
Hi,
Thanks for sharing back what solved the issue for you.
We are glad everything is working now.
Give us a note if you need any further assistance.
Kind regards,
Thodoris
Hi,
Thanks for sharing back what solved the issue for you.
We are glad everything is working now.
Give us a note if you need any further assistance.
Kind regards,
Thodoris