jasonbrooks added a new comment to an issue you are following:
``
How does this look?
@dwalsh
=== systemd-Based Containers ===
A systemd-based container includes the systemd system and service manager as part of its
image in order to run one or more systemd-managed services within a single container, to
take advantage of systemd's zombie-reaping capabilities, or to better handle container
logging.
systemd-based containers' Dockerfiles have the following differences:
==== LABELS ====
Run/Usage: systemd-based containers should include a Run or Usage label that directs users
to include "--tmpfs /run", "--tmpfs /tmp", and "-v
/sys/fs/cgroup:/sys/fs/cgroup", which systemd requires to run. Container hosts
running the default Fedora docker package and the oci-systemd-hook don't require these
run options, but they should be included for compatibility with other container hosts.
For example:
<pre>
LABEL Usage="docker run -d -P --tmpfs /run --tmpfs /tmp -v
/sys/fs/cgroup:/sys/fs/cgroup -v owncloud-data:/var/lib/owncloud -v
owncloud-config:/etc/owncloud owncloud"
</pre>
==== CMD/ENTRYPOINT ====
systemd-based containers must include "/sbin/init" as an ENTRYPOINT or CMD,
which will start systemd inside the container at run time. systemd will start up and
manage services enabled with the Dockerfile using the standard "systemctl enable
foo" commands in RUN statements.
For example:
<pre>
FROM fedora:25
ENV container=oci
RUN dnf -y install httpd; dnf clean all; systemctl enable httpd
EXPOSE 80
CMD [ "/sbin/init" ]
</pre>
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/233