Closed amake closed 5 years ago
I should note that downstream containers can work around this issue by running the following before calling apt-get update
:
RUN echo 'deb http://deb.debian.org/debian jessie main' > /etc/apt/sources.list \
&& echo 'deb http://security.debian.org/debian-security jessie/updates main' >> /etc/apt/sources.list
Triggered build. Hope this works and does not break anything. I'm currently not using those images. Thus if there are any issue it would be great, if you could come back to me.
Thanks for bringing this up!
This container's base is
debian:jessie
; Jessie is no longer receiving updates, so thejessie-updates
apt source has been taken down. This makes runningapt-get update
fail in a container with an old source list. For instance trying to buildsuchja/wine
:Here are the apt sources for your container:
Here are the sources in the latest
debian:jessie
(7cd9fb1ee74f
):I have a container downstream of
suchja/wine
that currently can't build due to this issue; if you could simply trigger a new build of this project andsuchja/wine
, thus updating the sources list, that would be great.