oposs
Unable to run without the --privileged option
Thanks for the demo, it is very useful. I was able to connect with thinlinc but with the --privileged option. When I tried the Pro Tip I have the following error. Any ideas of what the problem could be? I am running on a MacBook Monterey 12.7.6 and Docker desktop 4.35.1. Thanks and best regards!
docker run -v /sys/fs/cgroup/:/sys/fs/cgroup:ro
--tmpfs /run --tmpfs /run/lock
--pull=always
--cap-add SYS_PTRACE --cap-add SYS_ADMIN
--name my-tl-demo --publish 9922:22 -t
oposs/tl-ubuntu
latest: Pulling from oposs/tl-ubuntu
Digest: sha256:9f927aadff367a7186f02f24806e344f01d8862cc67dba83272a99edbb353cf7
Status: Image is up to date for oposs/tl-ubuntu:latest
systemd 249.11-0ubuntu3.12 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
Detected virtualization docker.
Detected architecture x86-64.
Welcome to Ubuntu 22.04.4 LTS!
Failed to create /init.scope control group: Read-only file system Failed to allocate manager object: Read-only file system [!!!!!!] Failed to allocate manager object. Exiting PID 1... make: *** [image_unprivileged] Error 255
Hi André
this only works on linux based hosts unfortunately
cheers tobi
----- On Nov 15, 2024, at 9:15 PM, André Plante @.***> wrote:
Thanks for the demo, it is very useful. I was able to connect with thinlinc but with the --privileged option. When I tried the Pro Tip I have the following error. Any ideas of what the problem could be? I am running on a MacBook Monterey 12.7.6 and Docker desktop 4.35.1. Thanks and best regards!
docker run -v /sys/fs/cgroup/:/sys/fs/cgroup:ro --tmpfs /run --tmpfs /run/lock --pull=always --cap-add SYS_PTRACE --cap-add SYS_ADMIN --name my-tl-demo --publish 9922:22 -t oposs/tl-ubuntu latest: Pulling from oposs/tl-ubuntu Digest: sha256:9f927aadff367a7186f02f24806e344f01d8862cc67dba83272a99edbb353cf7 Status: Image is up to date for oposs/tl-ubuntu:latest systemd 249.11-0ubuntu3.12 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified) Detected virtualization docker. Detected architecture x86-64.
Welcome to Ubuntu 22.04.4 LTS!
Failed to create /init.scope control group: Read-only file system Failed to allocate manager object: Read-only file system [!!!!!!] Failed to allocate manager object. Exiting PID 1... make: *** [image_unprivileged] Error 255
— Reply to this email directly, [ https://github.com/oposs/tl-docker/issues/7 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AADIZX57TCUU5DHBKU6RSHL2AZI73AVCNFSM6AAAAABR34M2XSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGY3DGMBRHE4DIOA | unsubscribe ] . You are receiving this because you are subscribed to this thread. Message ID: @.***>
-- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland www.oetiker.ch @.*** +41 62 775 9902
