-
Notifications
You must be signed in to change notification settings - Fork 97
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
🐛 Move kairos vars to their own file #2908
Conversation
Otherwise when creating derivatives, the upgrades can overwrite the existing kairos release info adn break the whole thing. This patch adds the variables into a new /]etc/kairos-release file, as well as keeping them in the usual /etc/os-release file for backwards compatibility Signed-off-by: Itxaka <[email protected]>
Signed-off-by: Itxaka <[email protected]>
Signed-off-by: Itxaka <[email protected]>
Signed-off-by: Itxaka <[email protected]>
This needs an updated agent bundled with the changes in order to work |
New framework image should be built to test this with changes to:
|
Welp, seems to work? Wtf. Okay, cutting new framework and os builder version |
Signed-off-by: Itxaka <[email protected]>
Now ready to be reviewed finally :D |
Hello, When upgrading within kubernetes from e.g. 22.04-standard-amd64-generic-v3.2.2-k3sv1.30.5-k3s1 the upgrade gives below error and can not be applied making a symbolic link works as a workaround ln -s /etc/os-release /etc/kairos-release `+ HOST_DIR=/host
|
@Wolverine65 thanks, opened a ticket on #3010 |
Otherwise when creating derivatives, the upgrades can overwrite the existing kairos release info adn break the whole thing.
This patch adds the variables into a new /]etc/kairos-release file, as well as keeping them in the usual /etc/os-release file for backwards compatibility
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Part of: #2907