Skip to content

Commit

Permalink
Merge pull request #370 from flatcar/tormath1/docker
Browse files Browse the repository at this point in the history
docker: remove legacy doc and add sysext removal snippet
  • Loading branch information
tormath1 authored Nov 5, 2024
2 parents 4e7af08 + c9336e8 commit 5cd8ecb
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 155 deletions.

This file was deleted.

16 changes: 16 additions & 0 deletions content/docs/latest/provisioning/sysext/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,22 @@ The table below give an overview on the supported Flatcar extensions.
Users can enable Flatcar extensions by writing one name per line to `/etc/flatcar/enabled-sysext.conf`.
For now there are no pre-enabled release extensions but once Flatcar would move parts of the base image out into extensions, these would be pre-enabled as entries in `/usr/share/flatcar/enabled-sysext.conf`. They can be disabled with a `-NAME` entry in `/etc/flatcar/enabled-sysext.conf`.

### Remove Docker and / or Containerd from Flatcar

If Flatcar is used as a Kubernetes node or one wants to try a different version of Docker or Containerd, it is possible to remove those extensions from Flatcar at boot using this configuration:
```yaml
variant: flatcar
version: 1.0.0
storage:
links:
- path: /etc/extensions/docker-flatcar.raw
target: /dev/null
overwrite: true
- path: /etc/extensions/containerd-flatcar.raw
target: /dev/null
overwrite: true
```
## Community supported extensions ("community supported")
A simple way to extend Flatcar is to use the systemd-sysext images from the [sysext-bakery GitHub repo](https://github.com/flatcar/sysext-bakery). It [publishes prebuilt images](https://github.com/flatcar/sysext-bakery/releases) that bundle third-party binaries. The repo README provides a Butane config example for updating the extensions with `systemd-sysupdate`.
Expand Down

0 comments on commit 5cd8ecb

Please sign in to comment.