Actions
Bug #35502
closed
Cannot start Foreman in docker container - "Could not find init script for 'systemd-journald'" and other issues
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Unattended installations
Target version:
-
Description
Hello everyone,
I'm trying to test-run Foreman by running it in a docker container, but I'm having trouble running the installer, as it throws several systemd-related issues, like
[ERROR ] [configure] /Stage[main]/Systemd::Journald/Service[systemd-journald]/ensure: change from 'stopped' to 'running' failed: Could not find init script for 'systemd-journald'
and
/Stage[main]/Puppet::Agent::Service::Daemon/Service[puppet]/ensure: change from 'stopped' to 'running' failed: Could not find init script for 'puppet'
The Dockerfile is in the attachments, and I'm starting the container by running
docker run -it -h example.com --add-host example.com:172.17.0.2 foreman-test
Any help getting this up and running would be appreciated. Otherwise, you could suggest how I could test foreman with some raspberry pis without breaking my only x86 system that I have.
Files
Updated by Ewoud Kohl van Wijngaarden over 1 year ago
- Status changed from New to Rejected
The installer is not meant to run inside a container. It assumes a real system. At this moment we don't officially support Docker images.
Actions