I would have to at very least chown the subdirectory to the same user the
container is running on in order to have write access to it from with in the
container, but that was my thought that the volume itself provides enough
protection. My friend who is an experienced systems administrator seems
On August 14, 2016 9:55:36 AM EDT, Personal wrote:
>I would have to at very least chown the subdirectory to the same user
>the container is running on in order to have write access to it from
>with in the container, but that was my thought that the volume itself
>provides enough protection. My fri
I would have to at very least chown the subdirectory to the same user the
container is running on in order to have write access to it from with in the
container, but that was my thought that the volume itself provides enough
protection. My friend who is an experienced systems administrator seems
Hello Zach,
> Gluster Volume subdirectories Bind Mounted into their respective containers
> (i.e. /data/gluster/user1 -> container:/data/gluster)
Considering this line, do you even depend on ACLs? I'd think bind mounts
provide sufficient protection by itself, as long as server demons run outsid
Hey guys, I have a crucial decision I have to make about a platform I’m
building, and I really need your help to make this decision in regards to
security. Here’s what I’m trying to accomplish:
Platform: Highly Available Wordpress hosting using Galera, GlusterFS & LXD
(don’t worry about the SQL
