Can’t run systemd in Debian container from Debian host #15965
Yvan-Masson
started this conversation in
General
Replies: 4 comments 15 replies
-
Please include a full |
Beta Was this translation helpful? Give feedback.
5 replies
-
Could you try FROM docker.io/library/debian:bullseye |
Beta Was this translation helpful? Give feedback.
9 replies
-
BTW This looks like I fixed it in podman 4. |
Beta Was this translation helpful? Give feedback.
1 reply
-
Thank you for your reply.
Can you suggest, please, docs, books, materials - where to get related
systems programming/theory materials? How this command can be observed?
…On Tue, Jan 14, 2025, 22:19 Daniel J Walsh ***@***.***> wrote:
Something like
podman exec CTRID kill SIGRTMIN+3 1
Should work.
—
Reply to this email directly, view it on GitHub
<#15965 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BLX2UAMZVA23GAOBV6SAA4T2KVPLNAVCNFSM6AAAAABU3SIZ4CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBTGUYTINY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
From a Debian testing host running Podman 3.4.7, running systemd in a Debian stable container fails with error
Trying to run as user instance, but the system has not been booted with systemd.
, but it works if I append/lib/systemd/systemd
to thepodman run
command.Steps to reproduce the issue:
podman run localhost/my_image:latest
.Describe the results you received:
It fails with error
Trying to run as user instance, but the system has not been booted with systemd.
. Note that usingsystemd=always
does not help.Describe the results you expected:
The container should be able to run.
Additional information you deem important (e.g. issue happens only occasionally):
However, if I run the same image with
podman run localhost/my_image:latest /lib/systemd/systemd
then it works perfectly. Also, runningpodman run registry.access.redhat.com/ubi8-init
works as intended.Output of
podman version
:Output of
podman info
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
I first asked on [email protected], where I was told to report the issue upstream.
I did not test with latest upstream version (4.2.0) because it is still in Debian experimental and I would prefer avoid messing with my system if possible.
I have read the troubleshooting guide, but could not find anything related. I have also read changelogs from 3.4.7 to 4.2.0 and could not find something related to my issue, but I maybe I just missed it.
Additional environment details (AWS, VirtualBox, physical, etc.):
It is a physical host.
Beta Was this translation helpful? Give feedback.
All reactions