You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 2, 2024. It is now read-only.
Expected outcome:
Install should complete successfully with the message "Install complete"
Actual outcome:
WARNING: No swap limit support
---> Installing [email protected]
---> Installing template unit-file: /media/root/etc/systemd/system/[email protected]
---> Populating drop-in: /media/root/etc/systemd/system/[email protected]/10-override.conf
---> Removing template unit-file: /media/root/etc/systemd/system/[email protected]
---> Removing /media/root/etc/systemd/system/[email protected]
Failed to connect to bus: No data available
---> Enabling [email protected]
Failed to connect to bus: No data available
Failed to connect to bus: No data available
---> Releasing host mounted container
WARNING: No swap limit support
---> Restarting [email protected]
-- Logs begin at Thu 2019-02-28 09:04:59 UTC. --
Failed to connect to bus: No data available
Failed to connect to bus: No data available
---> Install error
Review the status for additonal information: systemctl status [email protected]
The text was updated successfully, but these errors were encountered:
jdeathe
changed the title
SCMI installation with systemd manager option fails on Ubuntu hosts.
SCMI installation with systemd manager option fails on CoreOS/Ubuntu hosts.
Mar 4, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue is only known to effect CoreOS and Ubuntu hosts it does not effect any of the EL based hosts such as CentOS-7, Centos Atomic Host.
Docker host environment details used to replicate this issue
Environment 1.
Environment 2 (inc. Docker CE).
When scmi attempts to run systemctl commands in the chroot that allows the container to run commands on the host the following error is returned.
To reproduce:
Expected outcome:
Install should complete successfully with the message "Install complete"
Actual outcome:
The text was updated successfully, but these errors were encountered: