jasder
/
runc
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge pull request #1414 from jwendell/1413 

Update examples on README to allow rootless execution
This commit is contained in:
Michael Crosby 2017-04-21 17:33:05 -07:00 committed by GitHub
parent 9f1ef73ef9 d8477f9b02
commit e62817fefc
1 changed files with 18 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
README.md
View File

@ -117,8 +117,8 @@ Assuming you have an OCI bundle from the previous step you can execute the conta
The first way is to use the convenience command `run` that will handle creating, starting, and deleting the container after it exits. The first way is to use the convenience command `run` that will handle creating, starting, and deleting the container after it exits.
```bash ```bash
# run as root
cd /mycontainer cd /mycontainer
runc run mycontainerid runc run mycontainerid
``` ```
@ -165,8 +165,8 @@ Now we can go though the lifecycle operations in your shell.
```bash ```bash
# run as root
cd /mycontainer cd /mycontainer
runc create mycontainerid runc create mycontainerid
# view the container is created and in the "created" state # view the container is created and in the "created" state
@ -185,6 +185,22 @@ runc delete mycontainerid
This adds more complexity but allows higher level systems to manage runc and provides points in the containers creation to setup various settings after the container has created and/or before it is deleted. This adds more complexity but allows higher level systems to manage runc and provides points in the containers creation to setup various settings after the container has created and/or before it is deleted.
This is commonly used to setup the container's network stack after `create` but before `start` where the user's defined process will be running. This is commonly used to setup the container's network stack after `create` but before `start` where the user's defined process will be running.
#### Rootless containers
`runc` has the ability to run containers without root privileges. This is called `rootless`. You need to pass some parameters to `runc` in order to run rootless containers. See below and compare with the previous version. Run the following commands as an ordinary user:
```bash
# Same as the first example
mkdir ~/mycontainer
cd ~/mycontainer
mkdir rootfs
docker export $(docker create busybox) | tar -C rootfs -xvf -
# The --rootless parameter instructs runc spec to generate a configuration for a rootless container, which will allow you to run the container as a non-root user.
runc spec --rootless
# The --root parameter tells runc where to store the container state. It must be writable by the user.
runc --root /tmp/runc run mycontainerid
```
#### Supervisors #### Supervisors
`runc` can be used with process supervisors and init systems to ensure that containers are restarted when they exit. `runc` can be used with process supervisors and init systems to ensure that containers are restarted when they exit.