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.

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.

I can recommend purelymail.com. Cheap, works great with my custom domain, allows unlimited mail boxes ans users for the whole family.

Until August 2024 only .arpa was reserved for residential network services. Glad to hear there is something new less akward!

I’m using syncthing-fork on Android for years on multiple devices without problems.

Get a mainboard and CPU supporting ECC ram. Combine it with ZFS as the file system. With this setup you are safe from bitrot.

True, but I thought we are talking about security here…?

How would is a typo possible if one is using a password manager?

Tell me

Did you read my message? After one failed attempt you will get banned.

30 character password + fail2ban after one failed attempt. Why not?

Create a sudo rule which allows the user to run only this exact command: “sudo docker restart mycontainer”

Problem with Joplin: The raw files are randomly named so you can’t easily find a specific note