Some useful suggestions were made in commit 5411e69b ("Update the docker
containers"). This captures them in a more visible place.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
To avoid proliferation of versions, I suggest the following policy: the
oldest LTS release still receiving maintenance updates + the most recent
release for distributions that offer LTS releases.
For CentOS, this means CentOS7 and CentOS Stream 9 (since CentOS are all
"long-term support", this is just the oldest and the newest among
currently supported).
For Ubuntu, this means Ubuntu 18.04 (previous LTS are in "security fixes
only" mode) and Ubuntu 21.10. Recent Ubuntu attempts to be interactive
during the configuration of tzdata, required some additional setup.
In the common installation script, the logic for handling a
configured/built local directory breaks if `gmake` is detected as the
make binary; `make distclean` then fails inside the container because
not all systems have `gmake` symlink. Remove that attempt of a
workaround completely, just require that the host directory is clean.
Signed-off-by: Alexey Neyman <stilor@att.net>
The name of the docker images have changed on docker hub. Update the
name used to point to the official archlinux image.
Fixes#1522
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Recent Linux kernels (5.3 and newer) use rsync to copy headers around.
Add the rsync package to the list of dependencies.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Make the creation of docker images easier so that CTNG_UID/CTNG_GID have
a default value if it's not explicitly specified when building. This
will allow publishing of images on various package repositories (e.g.
docker hub, gitlab containers). dmgr.sh can still be used to set the
UID/GID to that of the current user when building a custom container.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
... and add Mint 19 and CentOS 6. The latter currently fails in
ctng's configure due to an old libtool; need to make libtool
optional.
Signed-off-by: Alexey Neyman <stilor@att.net>
There is a subtle difference when executable bit is a part of the umask.
And at least some versions (Debian/stretch) fail if the resulting mode
would've been different if not for the umask setting.
Fixes#998.
Although, with such chmods/umasks it is likely that some package installation
will break anyway. But I'll leave it until somebody complains.
Signed-off-by: Alexey Neyman <stilor@att.net>
Also, build containers with --no-cache: distributions like ArchLinux
retire their packages very quickly, need to always use up-to-date
package databases.
Signed-off-by: Alexey Neyman <stilor@att.net>
