|
Dear
systemd users,
I experimenting with running systemd in a container, the container engine I am using is docker (I know is not ideal but this
is a hard requirement for now).
I start the container like this:
CMD ["/usr/lib/systemd/systemd",
"--system",
"--default-standard-output=fd",
"--default-standard-error=fd:stdout"]
But this seems to break something because neither journald nor dbus processes runs
The issue
is with the flags --default-standard-output
and --default-standard-error
because everything seems ok if those are removed from the command.
Any
idea why --default-standard-output=fd
--default-standard-error=fd:stdout breaks
systemd?
thank you
|
problem starting systemd in a container using parameters --default-standard-output=fd --default-standard-error=fd:stdout
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: problem starting systemd in a container using parameters --default-standard-output=fd --default-standard-error=fd:stdout
- From: masber masber <masber@xxxxxxxxxxx>
- Date: Wed, 30 Mar 2022 17:25:45 +0000
- Accept-language: en-AU, en-GB, en-US
- Suggested_attachment_session_id: 95102f96-274f-25c4-12a0-c83bc3a5aac7
- Follow-Ups:
- Prev by Date: systemd prerelease 251-rc1
- Next by Date: udevadm: Failed to scan devices: Input/output error
- Previous by thread: systemd prerelease 251-rc1
- Next by thread: Re: problem starting systemd in a container using parameters --default-standard-output=fd --default-standard-error=fd:stdout
- Index(es):
 |