|
|
@@ -6,9 +6,10 @@ These images contain [Scientific Linux](http://www.scientificlinux.org/).
|
|
|
|
|
|
## About Scientific Linux
|
|
|
|
|
|
-Scientific Linux is a [Fermilab](http://fnal.gov/) sponsored project. Our primary user base is within the High Energy and High Intensity Physics community. However, our users come from a wide variety of industries with various use cases all over the globe – and sometimes off of it!
|
|
|
+Scientific Linux is a [Fermilab](http://fnal.gov/) sponsored project. Our primary user base is within the High Energy and High Intensity Physics community. However, our users come from a wide variety of industries with various use cases all over the globe – and sometimes off of it!
|
|
|
|
|
|
Our Mission:
|
|
|
+
|
|
|
> Driven by Fermilab’s scientific mission and focusing on the changing needs of experimental facilities, Scientific Linux should provide a world class environment for scientific computing needs.
|
|
|
|
|
|
Scientific Linux is a rebuild of Red Hat Enterprise Linux (property of Red Hat Inc. NYSE:RHT).
|
|
|
@@ -29,9 +30,9 @@ The root filesystem for these docker images is built on our internal build syste
|
|
|
|
|
|
## Getting Help
|
|
|
|
|
|
-* [SL Faq](https://www.scientificlinux.org/documentation/faq)
|
|
|
+- [SL Faq](https://www.scientificlinux.org/documentation/faq)
|
|
|
|
|
|
-* [Email Lists](https://www.scientificlinux.org/community)
|
|
|
+- [Email Lists](https://www.scientificlinux.org/community)
|
|
|
|
|
|
## Docker, overlayfs, and yum
|
|
|
|
|
|
@@ -39,12 +40,14 @@ Recent Docker versions support the [overlayfs](https://docs.docker.com/engine/us
|
|
|
|
|
|
## Package docs and licence files
|
|
|
|
|
|
-By default the SL docker images do not include these files. If you require them, please remove `tsflags=nodocs` from `/etc/yum.conf` and run `yum reinstall mypackage` to recieve the documentation.
|
|
|
+By default the SL docker images do not include these files. If you require them, please remove `tsflags=nodocs` from `/etc/yum.conf` and run `yum reinstall mypackage` to recieve the documentation.
|
|
|
|
|
|
---
|
|
|
+
|
|
|
# Quick Reference
|
|
|
|
|
|
## Example Usage
|
|
|
+
|
|
|
You can try out the containers via:
|
|
|
|
|
|
```console
|
|
|
@@ -54,7 +57,8 @@ $ docker run -it %%IMAGE%%:7 cat /etc/redhat-release
|
|
|
```
|
|
|
|
|
|
## Enabling systemd in SL7
|
|
|
-The SL7 docker container ships with systemd mostly functional. You can build a SL7 systemd enabled container with the following Dockerfile
|
|
|
+
|
|
|
+The SL7 docker container ships with systemd mostly functional. You can build a SL7 systemd enabled container with the following Dockerfile.
|
|
|
|
|
|
In order to run a container with systemd, you will need to mount the cgroups volumes from the host.
|
|
|
|
|
|
@@ -71,13 +75,14 @@ CMD ["/usr/sbin/init"]
|
|
|
```
|
|
|
|
|
|
You can build and run this example (with apache) via:
|
|
|
+
|
|
|
```console
|
|
|
$ docker build --rm -t local/mycontainer your/path
|
|
|
$ docker run -ti -v /sys/fs/cgroup:/sys/fs/cgroup:ro -p 80:80 local/mycontainer
|
|
|
```
|
|
|
+
|
|
|
Which will run systemd within the container in a limited context.
|
|
|
|
|
|
It is recommended that you install any relevant [OCI hooks](https://www.opencontainers.org/) for your container host - such as `oci-register-machine` or `oci-systemd-hook`.
|
|
|
|
|
|
Some container hosts must add `--tmpfs /run` to the `docker run` command.
|
|
|
-
|