remove default "containerd.toml" config file#215
Conversation
|
LGTM |
|
whoops; missed a reference to that file in the rpm spec; pushing a fix now |
d5add94 to
e7bc510
Compare
This configuration file was used to disable the CRI plugin to work around an issue where CRI was automatically listening for remote connections. That problem was resolved, so we no longer need a customized configuration. Signed-off-by: Sebastiaan van Stijn <[email protected]>
e7bc510 to
37e406c
Compare
| %{_unitdir}/containerd.service | ||
| %{_sysconfdir}/containerd | ||
| %{_mandir}/man*/* | ||
| %config(noreplace) %{_sysconfdir}/containerd/config.toml |
There was a problem hiding this comment.
This is the only part I was looking at if this could have side-effects (file and directory no longer marked as "config"). I think it should have no consequences (package no longer knows of this path, so won't interfere with it), but if someone knows if this is a concern, let me know.
There was a problem hiding this comment.
@thaJeztah removing this does have some impact on rpm users who are currently overwriting the rpm supplied config.toml with their own. This being removed above, causes the user supplied override config.toml file also to be deleted, when they upgrade to a rpm version with this change. rpm moves the file to.rpmsave/.rpmnew after upgrading to the new version with the above change.
Can we just continue shipping an empty config.toml with just version=2 without the disabled cri plugin config ?
There was a problem hiding this comment.
@ravilr hmmm... yeah, we could partially revert that change if there's no other way; do you know if rpms allow for the change to be "ignored" (as in: don't touch the existing file?)
There was a problem hiding this comment.
according to https://rpm-packaging-guide.github.io/#files, %config(noreplace) exists to protect local modifications to a config file, so that local edits to config files won't get lost during a subsequent upgrade.
But, since the file is being removed from rpm, that doesn't apply here.
IMO, if the intention is to get rid of disabling of cri plugin, then rpm packaging here should continue shipping an empty config.toml with %config(noreplace).
|
Nice! 👍 Debian has a We probably need a |
@tianon IIUC, you mean "add a script that removes the config file when installing the new package"? I wonder if we should do that; even though we provided a "default", we also marked the file as Or do you mean the "reverse"; prevent the default behavior of |
|
Discussed in maintainers meeting with @thaJeztah @cpuguy83; the config file we were installing is very benign and shouldn't cause problems for any existing users if it doesn't get cleaned up (and the chance of breaking changes to that config file syntax are low), so this is purely a perfectionism / cleanliness concern and should be relatively harmless to ignore. In other words, we do not need to include |
|
fwiw, rm_conffile in dpkg-maintscript-helper will not remove conffile if it has been modified by users. dpkg has md5sum of the conffile which is used when removing. |
ha, seems i misread the above discussion... (just to ignore that) |
No worries; thanks for looking! Yes, we discussed for a bit, and thought it was not worth the extra complexity to clean up the file (which is mostly harmless) |
|
@silvin-lubecki @tiborvass ptal; this one good to go? |
|
@tiborvass ptal |
|
Given that this fix is not critical, and it's been pending for a while, I think it should be ok to merge this after #223 has been merged and released (keeping the diff for that release small, as it's a security release, so better to not include too many other changes) |
|
@thaJeztah #223 has been merged and it has been released as Docker Engine 20.10.6. So I think we can merge this PR now. |
|
Ah, yes, let's get this one in 👍 |
This reverts commit 37e406c. Relates to docker#215 (comment) > removing this does have some impact on rpm users who are currently overwriting > the rpm supplied config.toml with their own. This being removed above, causes > the user supplied override config.toml file also to be deleted, when they upgrade > to a rpm version with this change. rpm moves the file to.rpmsave/.rpmnew after > upgrading to the new version with the above change. Reverting this change (at least temporarily until we figure out an alternative) is the safest option for now. Signed-off-by: Sebastiaan van Stijn <[email protected]>
|
Opened #233 to (temporarily) revert while we figure out an approach for #215 (comment) |
This configuration file was used to disable the CRI plugin to work around an
issue where CRI was automatically listening for remote connections.
That problem was resolved, so we no longer need a customized configuration.
Addresses containerd/containerd#4956