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 Feb 13, 2023. It is now read-only.
linux 5.11.15.arch1-2
docker 1:20.10.6-1
docker-compose 1.29.1-1
dbus 1.12.20-1
dbus-glib 0.112-1
Your OS
Linux Archlinux
Full console output
root@7579bc3d9031:/# systemctl
Failed to connect to bus: No such file or directory
Summary
After a recent update (not updated for a long time), systemctl stopped starting in the container. It turns out that drupalvm in docker does not work in archlinux now. The configuration is standard.
For the test, I raised the image of debian bullseye (Linux bullseye 5.10.0-5-amd64, Docker version 20.10.5+dfsg1, dbus 1.12.20-2) to vagrant - the same result. In the image of debian 10 raised in the vagrant it works normally.
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
Issue Type
Your Environment
linux 5.11.15.arch1-2
docker 1:20.10.6-1
docker-compose 1.29.1-1
dbus 1.12.20-1
dbus-glib 0.112-1
Your OS
Full console output
root@7579bc3d9031:/# systemctl
Failed to connect to bus: No such file or directory
Summary
After a recent update (not updated for a long time), systemctl stopped starting in the container. It turns out that drupalvm in docker does not work in archlinux now. The configuration is standard.
The text was updated successfully, but these errors were encountered: