You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
website build broken during Docker image preparation #3382
root@infra-digitalocean-ubuntu1604-x64-1:~# docker run -it --rm node:lts-bullseye bashroot@8526f963090e:/# apt-get update && apt-get install -y rsyncGet:1 http://deb.debian.org/debian bullseye InRelease [116 kB]Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB]Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]Get:4 http://deb.debian.org/debian bullseye/main amd64 Packages [8183 kB]Get:5 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages [245 kB]Get:6 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [14.8 kB]Fetched 8651 kB in 2s (4689 kB/s)Reading package lists... DoneReading package lists... DoneBuilding dependency tree... DoneReading state information... DoneThe following additional packages will be installed: libpopt0Suggested packages: openssh-serverThe following NEW packages will be installed: libpopt0 rsync0 upgraded, 2 newly installed, 0 to remove and 3 not upgraded.Need to get 446 kB of archives.After this operation, 987 kB of additional disk space will be used.Get:1 http://deb.debian.org/debian bullseye/main amd64 libpopt0 amd64 1.18-2 [49.6 kB]Get:2 http://deb.debian.org/debian bullseye/main amd64 rsync amd64 3.2.3-4+deb11u1 [396 kB]Fetched 446 kB in 0s (10.6 MB/s)debconf: delaying package configuration, since apt-utils is not installedSelecting previously unselected package libpopt0:amd64.(Reading database ... 22794 files and directories currently installed.)Preparing to unpack .../libpopt0_1.18-2_amd64.deb ...Unpacking libpopt0:amd64 (1.18-2) ...Selecting previously unselected package rsync.Preparing to unpack .../rsync_3.2.3-4+deb11u1_amd64.deb ...Unpacking rsync (3.2.3-4+deb11u1) ...Setting up libpopt0:amd64 (1.18-2) ...Setting up rsync (3.2.3-4+deb11u1) ...invoke-rc.d: could not determine current runlevelinvoke-rc.d: policy-rc.d denied execution of start.Processing triggers for libc-bin (2.31-13+deb11u6) ...root@8526f963090e:/#
root@infra-digitalocean-ubuntu1604-x64-1:~# docker imagesREPOSITORY TAG IMAGE ID CREATED SIZEnode lts aa392f56f466 12 hours ago 1.09GBnode lts-bookworm aa392f56f466 12 hours ago 1.09GBnode lts-bullseye 78b037dbb659 3 weeks ago 996MB
Oddly I can't reproduce the failures with node:lts/node:lts-bookworm on a separate machine.
As another datapoint, I tried node:lts-bookworm on test-digitalocean-ubuntu1804-docker-x64-1 and the failing apt update command passes there. That machine is running
FWIW using --security-opt=seccomp:unconfined to start the container allows the bookworm-based containers to run apt-get update && apt-get install -y rsync successfully. I'd rather keep running the production build with the working bullseye-based container than use that option.
Details
root@infra-digitalocean-ubuntu1604-x64-1:~# docker run -it --rm --security-opt=seccomp:unconfined node:lts bashroot@c946f84a1e5c:/# apt-get update && apt-get install -y rsyncGet:1 http://deb.debian.org/debian bookworm InRelease [147 kB]Get:2 http://deb.debian.org/debian bookworm-updates InRelease [52.1 kB]Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]Get:4 http://deb.debian.org/debian bookworm/main amd64 Packages [8904 kB]Get:5 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages [24.2 kB]Fetched 9176 kB in 2s (4859 kB/s)Reading package lists... DoneReading package lists... DoneBuilding dependency tree... DoneReading state information... DoneThe following additional packages will be installed: libpopt0Suggested packages: openssh-server python3-braceexpandThe following NEW packages will be installed: libpopt0 rsync0 upgraded, 2 newly installed, 0 to remove and 46 not upgraded.Need to get 461 kB of archives.After this operation, 1046 kB of additional disk space will be used.Get:1 http://deb.debian.org/debian bookworm/main amd64 libpopt0 amd64 1.19+dfsg-1 [43.3 kB]Get:2 http://deb.debian.org/debian bookworm/main amd64 rsync amd64 3.2.7-1 [417 kB]Fetched 461 kB in 0s (10.7 MB/s)debconf: delaying package configuration, since apt-utils is not installedSelecting previously unselected package libpopt0:amd64.(Reading database ... 23269 files and directories currently installed.)Preparing to unpack .../libpopt0_1.19+dfsg-1_amd64.deb ...Unpacking libpopt0:amd64 (1.19+dfsg-1) ...Selecting previously unselected package rsync.Preparing to unpack .../rsync_3.2.7-1_amd64.deb ...Unpacking rsync (3.2.7-1) ...Setting up libpopt0:amd64 (1.19+dfsg-1) ...Setting up rsync (3.2.7-1) ...invoke-rc.d: could not determine current runlevelinvoke-rc.d: policy-rc.d denied execution of start.Processing triggers for libc-bin (2.36-9) ...root@c946f84a1e5c:/#
I don't know if recent versions of Docker work on Ubuntu 16.04
Ubuntu 16.04 was released in 2016 and reached its end-of-life in April 2021 (unless you have a paid subscription with Canonical) so anything still using it should really be updated.
Activity
richardlau commentedon Jun 13, 2023
The failing command is
build/ansible/www-standalone/resources/scripts/build-site.sh
Line 47 in e96c917
which is failing on the infra machine:
node:ltsis the currently the same asnode:lts-bookwormand fails:but
node:lts-bullseyesucceeds:Oddly I can't reproduce the failures with
node:lts/node:lts-bookwormon a separate machine.mhdawson commentedon Jun 13, 2023
What are the versions of ubuntu on the passing/failing based machine? Maybe that is related.
mhdawson commentedon Jun 13, 2023
Just wondering since I see ubuntu1604 in the name of the website machine
richardlau commentedon Jun 13, 2023
That's because it is still running Ubuntu 16.04.
The other machine I was testing on is running RHEL 8.
targos commentedon Jun 13, 2023
Maybe this can be fixed by upgrading Docker, but I don't know if recent versions of Docker work on Ubuntu 16.04
www: use node:lts-bullseye in build-site.sh (#3383)
www: use node:lts-bullseye in build-site.sh
richardlau commentedon Jun 13, 2023
As another datapoint, I tried
node:lts-bookwormon test-digitalocean-ubuntu1804-docker-x64-1 and the failingapt updatecommand passes there. That machine is runningDocker version 24.0.1, build 6802122The RHEL 8 machine I am on is running
Docker version 20.10.12, build e91ed57while the www server is on
Docker version 20.10.7, build f0df350richardlau commentedon Jun 15, 2023
FWIW using
--security-opt=seccomp:unconfinedto start the container allows the bookworm-based containers to runapt-get update && apt-get install -y rsyncsuccessfully. I'd rather keep running the production build with the working bullseye-based container than use that option.Details
Daniel15 commentedon Jun 22, 2023
Ubuntu 16.04 was released in 2016 and reached its end-of-life in April 2021 (unless you have a paid subscription with Canonical) so anything still using it should really be updated.
www: use node:lts-bullseye in build-site.sh (#3384)
targos commentedon Feb 24, 2024
I think this can be closed. The website is not being built on this server anymore.
MoLow commentedon Feb 25, 2024
+1 closing. can reopen if needed