gilles/runon
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

clean README

Browse Source
This commit is contained in:
Gilles Grandou 2021-04-30 20:35:17 +02:00
parent 0dc48c6f9f
commit 6459d3d7a3
1 changed files with 11 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
README.md
View File

@ -22,7 +22,7 @@ Quick HOWTO
$ runon debian9 grep ^PRETTY_NAME /etc/os-release $ runon debian9 grep ^PRETTY_NAME /etc/os-release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)" PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
$ runon centos7 xclock $ runon centos7 xclock
[xclock launched!] [xclock launched!]
@ -106,14 +106,14 @@ keeping:
* `-v` verbose output, this is really usefull when running new * `-v` verbose output, this is really usefull when running new
containers for the first time, as the initial docker build can be containers for the first time, as the initial docker build can be
quite long (several minutes) especially with slow internet link. quite long (several minutes) especially with slow internet link.
If the command seems to be stalled, don't hesitate to interrupt it If the command seems to be stalled, don't hesitate to interrupt it
(with `CTRL-C`) and to restart it with `-v`. (with `CTRL-C`) and to restart it with `-v`.
* `-u` forces the container image to be updated, useful if the * `-u` forces the container image to be updated, useful if the
distribution has been updated and you want to use it. Otherwise, distribution has been updated and you want to use it. Otherwise,
if a container has been already built, it will be used directly if a container has been already built, it will be used directly
without doing any network access. without doing any network access.
* `-c <configfile>` uses a custom config file, useful to try new * `-c <configfile>` uses a custom config file, useful to try new
distribution without breaking your running config. distribution without breaking your running config.
@ -206,7 +206,7 @@ overriden in individual section.
* `dockerfile` the base content of dockerfile which will be used to * `dockerfile` the base content of dockerfile which will be used to
generate the running environment. There is usually no need to diverge generate the running environment. There is usually no need to diverge
from the ones given in example. from the ones given in example.
* `pkginstall` the dockerfile command used to install a package, likely * `pkginstall` the dockerfile command used to install a package, likely
to be standard for all `deb` and `rpm` based distributions. In the to be standard for all `deb` and `rpm` based distributions. In the
@ -217,7 +217,7 @@ overriden in individual section.
* `binds` the list of files and directories from the host system to * `binds` the list of files and directories from the host system to
expose in the container system. you might want to add `/opt` or other expose in the container system. you might want to add `/opt` or other
shared directories. See below for a description of `binds` entries shared directories. See below for a description of `binds` entries
* `environment` the list of environment variables you want to pass or * `environment` the list of environment variables you want to pass or
set in the container system. See below for a description set in the container system. See below for a description
@ -234,9 +234,9 @@ Some substitution happens upon reading the configuration:
Each `binds` line can have one of the following formats: Each `binds` line can have one of the following formats:
<hostpath> <hostpath>
<hostpath>:<mode> <hostpath>:<mode>
<hostpath>:<containerpath> <hostpath>:<containerpath>
<hostpath>:<containerpath>:<mode> <hostpath>:<containerpath>:<mode>
with: with:
@ -258,5 +258,3 @@ Each line can have one of the following formats:
If no value is given, the host value is passed into the container. If no value is given, the host value is passed into the container.