Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs/guidance: Talk about nesting containers #464

Merged
merged 1 commit into from
Apr 10, 2024
Merged

docs/guidance: Talk about nesting containers #464

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
20 changes: 20 additions & 0 deletions docs/src/building/guidance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,26 @@ Docker got started.
There's not much special to this that doesn't also apply
to application containers; but see below.

### Nesting OCI containers in bootc containers

The [OCI format](https://github.com/opencontainers/image-spec/blob/main/spec.md) uses
"whiteouts" represented in the tar stream as special `.wh` files, and typically
consumed by the Linux kernel `overlayfs` driver as special `0:0` character
devices. Without special work, whiteouts cannot be nested.

Hence, an invocation like

```
RUN podman pull quay.io/exampleimage/someimage
```

will create problems, as the `podman` runtime will create whiteout files
inside the container image filesystem itself.

Special care and code changes will need to be made to container
runtimes to support such nesting. Some more discussion in
[this tracker issue](https://github.com/containers/bootc/issues/128).

## systemd units

The model that is most popular with the Docker/OCI world
Expand Down