-
Notifications
You must be signed in to change notification settings - Fork 30
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.
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
Unable to disable pre-enabled extensions via enabled-sysext.conf #1481
Comments
Hi @2b, The file To deactivate the built-in sysext images: ...
storage:
links:
- path: /etc/extensions/docker-flatcar.raw
target: /dev/null
overwrite: true
- path: /etc/extensions/containerd-flatcar.raw
target: /dev/null
overwrite: true There is this tracking issue to enhance the documentation around sysext and to make it clearer for users: #1476 |
Hello @tormath1, Thank you for the explanation. That indeed wasn’t clear from the documentation. |
@2b did the suggested configuration has worked for you? |
It did, thank you. |
Ok, in this case I'm going to close this in favor of: #1476 (in which I referenced your issue). Thanks! |
Description
Adding
-EXTENSION_NAME
line into/etc/flatcar/enabled-sysext.conf
file doesn't disable pre-enabled extensions.Impact
Can't disable the Docker extension after enabling Podman.
Environment and steps to reproduce
-containerd
and-docker
lines into/etc/flatcar/enabled-sysext.conf
systemd-sysext list
still showscontainerd-flatcar
anddocker-flatcar
extensions.Expected behavior
Extensions should be disabled with a
-NAME
entry in/etc/flatcar/enabled-sysext.conf
, as stated in the documentation.Additional information
Extensions can be manually disabled by removing links from
/etc/extensions/
The text was updated successfully, but these errors were encountered: