You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ Running Docker or OCI runc containers with this executable, oci-systemd-hook is
11
11
When oci-systemd-hook detects systemd inside of the container it does the following:
12
12
13
13
* Mounts a tmpfs on /run and /tmp
14
-
- If there is content in the container image's /run and /tmp that content will be compied onto the tmpfs.
14
+
- If there is content in the container image's /run and /tmp that content will be copied onto the tmpfs.
15
15
* Creates a /etc/machine-id based on the the containers UUID
16
16
* Mounts the hosts /sys/fs/cgroups file systemd read-only into the container
17
17
- /sys/fs/cgroup/systemd will be mounted read/write into the container.
@@ -20,7 +20,7 @@ When the container stops, these file systems will be umounted.
20
20
21
21
systemd is expected to be able to run within the container without requiring
22
22
the `--privileged` option. However you will still need to specify a special `--stop-signal`. Standard docker containers sends SIGTERM to pid 1, but systemd
23
-
does not shut down properly when it recieves a SIGTERM. systemd specified that it needs to recieve a RTMIN+3 signal to shutdown properly.
23
+
does not shut down properly when it recieves a SIGTERM. systemd specified that it needs to receive a RTMIN+3 signal to shutdown properly.
24
24
25
25
If you created a container image based on a dockerfile like the following:
0 commit comments