search

rwilcox / odyssey

Rails, React, and deployment patterns
0 stars 0 forks source link

Removed `:z` from volume map in docker-compose file and added `sudo setenforce 0` to vagrant_setup.sh #12

Closed jcarvin closed 7 years ago

jcarvin commented 7 years ago

I believe this fixes the vagrant permissions issue. When I create a file in the docker container, I can now vagrant rsync-back on my local machine and it creates the file locally.

Let me know what your thoughts are.

rwilcox commented 7 years ago

I remain slightly skeptical, but this could be one of the reasons you were having permissioning problems.

This turns of SELinux, a system that can sit on top of the Centos dist of Linux. Originally built by the NSA (really), it's... well the protections I've seen in practice usually mean blocking applications from writing files. Which do present themselves as permission errors....

(In my experience, it's a 50% chance any particular Unix problem is "out of disk space" or "SELinux"...)

I don't think it solves the problem for everyone, but.. well it's a reasonable thing to turn off on developer VMs you're provisioning "yourself" through Vagrant. If it totally resolves it for you, awesome I guess!