Your message dated Thu, 18 Nov 2021 09:20:21 +0100
with message-id <[email protected]>
and subject line Re: Bug#999891: could not run system services within container
on debian 11.1 Bullseye
has caused the Debian Bug report #999891,
regarding could not run system services within container on debian 11.1 Bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
999891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999891
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 247.3-6
We are recently experimenting the Bullseye11.1 in our environment.
we have deployed kubernetes on Bullseye 11.1.
But we faced the issue when we run the application with container.
Application will start as a system service within container.
But in Bullseye 11.1 , we could not start the system service within
container.
we are getting the following issue.
following is the when we run with docker run command.
==============
Welcome to Debian GNU/Linux 11 (bullseye)!
Set hostname to <dc0fbafd2168>.
Failed to create /init.scope control group: No such file or directory
Failed to allocate manager object: No such file or directory
[!!!!!!] Failed to allocate manager object.
Exiting PID 1...
==================
This issue is appeared only on 11.1 But it is not present on
10.10(Buster)...
Reproduce Steps:
==============
docker run -it --tmpfs /run --tmpfs /run/lock --tmpfs /tmp --cap-add
SYS_ADMIN --privileged -v /etc/:/etc -v /sys/fs/cgroup:/sys/fs/cgroup
-p 8082:80 -t centos /sbin/init
In Buster, it is working fine. But in Bullseye, it is failing
Please solve this issue asap as so many were blocked due to this issue
Thanks,
Kannan V
--- End Message ---
--- Begin Message ---
On 18.11.21 08:00, Kannan V wrote:
Package: systemd
Version: 247.3-6
We are recently experimenting the Bullseye11.1 in our environment.
we have deployed kubernetes on Bullseye 11.1.
But we faced the issue when we run the application with container.
Application will start as a system service within container.
But in Bullseye 11.1 , we could not start the system service within
container.
we are getting the following issue.
following is the when we run with docker run command.
==============
Welcome to Debian GNU/Linux 11 (bullseye)!
Set hostname to <dc0fbafd2168>.
Failed to create /init.scope control group: No such file or directory
Failed to allocate manager object: No such file or directory
[!!!!!!] Failed to allocate manager object.
Exiting PID 1...
==================
This issue is appeared only on 11.1 But it is not present on
10.10(Buster)...
Reproduce Steps:
==============
docker run -it --tmpfs /run --tmpfs /run/lock --tmpfs /tmp --cap-add
SYS_ADMIN --privileged -v /etc/:/etc -v
/sys/fs/cgroup:/sys/fs/cgroup -p 8082:80 -t centos /sbin/init
In Buster, it is working fine. But in Bullseye, it is failing
Please solve this issue asap as so many were blocked due to this issue
Seems to be a docker issue:
https://serverfault.com/questions/1053187/systemd-fails-to-run-in-a-docker-container-when-using-cgroupv2-cgroupns-priva
Debian 11 (bullseye) defaults to cgroupv2
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
