-
Notifications
You must be signed in to change notification settings - Fork 75
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
bootc switch does not tell me when it ignores my /etc changes #438
Comments
I did #441 to try to expand on this more, but...yes. There is Bigger picture, dealing with drift in |
I added a bit more to the docs on this too, but a challenge here in a nutshell is everyone wants "just exactly the needed state and no more"...that's the hard part 😄 I saw https://grahamc.com/blog/erase-your-darlings/ go by a while ago and thought it was a great example of this "OK well, we can't keep track of everything writing to /etc so we'll make a new /persist directory". (I'm not sure that's really better myself) But at a practical level, we can encourage use of the transient |
I understand this is a quagmire. So here's my ideal /etc behavior. I am of course less informed than you, but I thought I'd write it down:
The above behavior also would fix some of #434 |
BTW a great example of stuff here to think about is the auto-generated SSH host keys, which get built on boot and live in The mental model here is that |
I've made changes to
/etc
in my Container file:Tag
quay.io/swalter/monday:test1
Tag
quay.io/swalter/monday:test2
If I modify
/etc/blah
on a deployed system, and then runbootc switch
the system ignores the changes represented in myContainerfile
, but doesn't tell me about this. This doesn't represent typical behavior I expect from a container. I expect the changes in/etc
to take effect, or at a minimum forbootc
to tell me when this isn't the case:The text was updated successfully, but these errors were encountered: