From b7067c4d8716cce0d061ae342791c7c20f12e395 Mon Sep 17 00:00:00 2001 From: Evgeny Vereshchagin Date: Sun, 12 Jul 2020 22:17:50 +0000 Subject: [PATCH] coverity: install systemd Apparently systemd is no longer installed in fedora containers by default ``` docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/sbin/init\": stat /sbin/init: no such file or directory": unknown. The command "$CI_MANAGERS/fedora.sh SETUP" failed and exited with 127 during . ``` --- travis-ci/managers/fedora.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/travis-ci/managers/fedora.sh b/travis-ci/managers/fedora.sh index 8fe43c0771..3a917564ed 100755 --- a/travis-ci/managers/fedora.sh +++ b/travis-ci/managers/fedora.sh @@ -65,11 +65,11 @@ for phase in "${PHASES[@]}"; do info "Setup phase" info "Using Fedora $FEDORA_RELEASE" # Pull a Docker image and start a new container - docker pull fedora:$FEDORA_RELEASE + printf "FROM fedora:$FEDORA_RELEASE\nRUN bash -c 'dnf install -y systemd'\n" | docker build -t fedora-with-systemd/latest - info "Starting container $CONT_NAME" $DOCKER_RUN -v $REPO_ROOT:/build:rw \ -w /build --privileged=true --name $CONT_NAME \ - -dit --net=host fedora:$FEDORA_RELEASE /sbin/init + -dit --net=host fedora-with-systemd/latest /sbin/init # Wait for the container to properly boot up, otherwise we were # running following dnf commands during the initializing/starting # (early/late bootup) phase, which caused nasty race conditions