Thank you, but this only applies to priviledged containers (which are normally not used and should not be used)
Thank you, but this only applies to priviledged containers (which are normally not used and should not be used)
Can you provide the required arguments for chroot? I’ve just opened the bash shell of a running container (docker exec -it mycontainer bash) and tried to “break out” using “chroot /”. I can’t access any files of the host.


I’ve notices the same (also 7800 XT with the latest stable kernel) and have used CoreCtrl to manually set the powersave profile. Before I thought this was somehow only happening on my machine, but now I think this is a bug…
How would a rogue container be able to access the root directory of the host? Wouldn’t it just be able to access the data on the docker volumes? Thank you.


How is “sync” the expected command to install a package?


Is the controller listed in the output of “lsusb”? What does the output of “journalctl -b” say when you plug in the controller?


What Xbox controller? 360? One? Wireless? Wired?
Regarding switching lanes I prefer when other driver enable their signal a few seconds just before they do the maneuver. If they enable their blinker too early I don’t know when exactly they will switch lanes which is confusing IMHO.