zlacker

>>makebo+(OP)
For my taste, container technology is pushing the OS too far. By typing:

    mount

you immediately see what I mean. Stuff that should be hidden is now in plain sight, and destroys the usefulness of simple system commands. And worse, the user can fiddle with the data structures. It's like giving the user peek and poke commands.

The idea of containers is nice, but they are a hack until kernels are re-architected.

>>ameliu+Q31
Sorry I am lacking the context to understand this post. What does running mount inside a container do that's so egregious? Are host mounts exposed to the container somehow? I thought everything needed to be explicitly passed through to the container (e.g. using a volume)?

>>throwa+Bc1
I think they mean that running `mount` on the host now lists hundreds of mountpoints from containers, snaps, packagekit etc.