Tag Info

New answers tagged

0

You must edit your /etc/sudoers file and grant your user permission to run some programs as root without password: yourusername ALL = (root) NOPASSWD: /path/to/prog1, /path/to/prog2, ... In your case, you can try: myusername ALL = (root) NOPASSWD: /bin/mkdir, /usr/bin/touch, /bin/grep You must check NOPASSWD entry is the last entry that match your ...


0

For anyone using ubuntu 14.04 apt-get flavor of docker. You just need to change the startup script to wait on "docker.io" and not "docker" like so: description "Docker startup script for yum_repo" author "me" start on filesystem and started docker.io stop on runlevel [!2345] respawn script /usr/local/bin/docker start -a yum_repo_run end script


2

LXC is a little bit better because it can run containers as unpriveleged users. This is not possible (AFAICT) with systemd-nspawn. If you want to know why docker, lxc, and systemd-nspawn are inherently not a solid security mechanism, read this: https://opensource.com/business/14/7/docker-security-selinux. Basically, containers still have access to the kernel ...


2

No matter the fancy name used here, both are solutions to a specific problem: A better segregation solution than classic Unix chroot. Operating system-level virtualization, containers, zones, or even "chroot with steriods" are names or commercial titles that defines the same concept of userspace separation, but with different features. Chroot was introduced ...



Top 50 recent answers are included