There is a way to perform some amount of kernel upgrade testing inside a container. Even though containers don’t run their own kernels, you can still install kernel packages inside containers, and upgrade them, so you can check that the package upgrades are correct.
However there is no way to verify that a kernel boots inside a container. To do that, you ...
The GitLab Runner images are based on either Ubuntu or Alpine Linux. This is stated in the docs:
The following Docker images are available:
gitlab/gitlab-runner:latest based on Ubuntu.
gitlab/gitlab-runner:alpine based on Alpine with much a smaller
footprint (~160/350 MB Ubuntu vs ~45/130 MB Alpine
Both Ubuntu ...
I found the solution to this shortly after posting this, and I feel a bit silly.
The problem was that I was merely setting a shell variable within ~/.bashrc and not exporting an envrionment variable.
Modify ~/.bashrc to use export:
export DOCKER_HOST=tcp://<userid>@<my server running the remote docker daemon>
instead of just:
This may not be possible on CentOS 7. The earliest version of CentOS 7 (7.0.1406) was already shipped with version 5.4.16 of the php package. You can verify this against the packages list in the CentOS Vault.
Remi's PHP repositories (the one currently mentioned in the Dockerfile) were intended to provide newer versions of PHP (>5.4) to CentOS. PHP 5.3 is ...
As GracefulRestart mentioned in the comment, you can build from systemd base image. For example, centos-systemd. But it's definitely not recommended to use systemd inside a docker container. Take a look at my related question.
If you need systemd only to meet dependencies, the better way is to ignore deb dependency.
This is not possible with standard network commands. Features that would make this easy were explicitly rejected by Docker a few years back (https://github.com/moby/moby/pull/8216).
You can of course manually move an interface into the network namespace of a Docker container, but this is fraught with problems: for example, any time you restart or re-create ...
I am assuming that you have added custom instructions to logrotate to rotate this file. If so, then a workaround may be to use copytruncate. man page
Truncate the original log file in place after creating a copy, instead of moving the old log file and optionally creating a new one. It can be used when some program cannot be told to close ...
I think the issue was that there was conflict & the system had'nt removed docker properly, even though I followed the instructions as per the official site.
However, what worked for me was purging everything docker related.
sudo apt-get purge docker-ce docker-ce-cli containerd.io docker-compose
Then I removed the docker folder from /var/lib folder.