Honestly the issue is docker was never designed to be a security boundary. Docker is always from the beginning a way to deploy application without conflicting shared library requirements. Looser than isolation of VM, but also not as hard as every other existing solution at that time (dedicated chroot, static linking, appimage, flatpak)
Yeah makes sense. I originally just went with docker because I didn’t want to bother to learn new stuff since spending hours solving issues at work made me less inclined to want to do the same at home when I just want to actual maybe work on “fun” stuff. Same reason I still use nginx instead of caddy. But I have seen increasingly more projects that use podman instead of docker so maybe I can still be lazy ish with my self hosting and get some security.
That’s the fun part. Podman skills transfer better to kubernetes if that’s your end goal. Docker compose has a different format than what a kubernetes YAML expect. So you do get a bit safer container model AND devops skills
Honestly the issue is docker was never designed to be a security boundary. Docker is always from the beginning a way to deploy application without conflicting shared library requirements. Looser than isolation of VM, but also not as hard as every other existing solution at that time (dedicated chroot, static linking, appimage, flatpak)
Yeah makes sense. I originally just went with docker because I didn’t want to bother to learn new stuff since spending hours solving issues at work made me less inclined to want to do the same at home when I just want to actual maybe work on “fun” stuff. Same reason I still use nginx instead of caddy. But I have seen increasingly more projects that use podman instead of docker so maybe I can still be lazy ish with my self hosting and get some security.
That’s the fun part. Podman skills transfer better to kubernetes if that’s your end goal. Docker compose has a different format than what a kubernetes YAML expect. So you do get a bit safer container model AND devops skills