-
Notifications
You must be signed in to change notification settings - Fork 12
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
container upgrade no longer works #623
Comments
troglobit
added a commit
that referenced
this issue
Sep 13, 2024
In 0edc2d5 and afbe5ca, just prior to v24.06.0-rc1, support for deleting containers in the background was added. However, this also broke support for upgrading containers. In afbe5ca the start script for containers was renamed from NAME.sh to S01-NAME.sh, but the container wrapper script's upgrade command was not updated. Neither was the cleanup and post-hook callbacks in confd! So when a container had been added to the system, the cleanup callback just simply deleted the script, preventing it from being recreated at ugprade This patch fixes the container identification code and also refactors the execd code to ensure that kill scripts (for deleting in background) and start scripts are run in the proper order *and* ensuring that execd also does not accidentally remove the container start script. Some cosmetic changes to the output at upgrade have also been added. Fixes #623 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Merged
13 tasks
troglobit
added a commit
that referenced
this issue
Sep 13, 2024
In 0edc2d5 and afbe5ca, just prior to v24.06.0-rc1, support for deleting containers in the background was added. However, this also broke support for upgrading containers. In afbe5ca the start script for containers was renamed from NAME.sh to S01-NAME.sh, but the container wrapper script's upgrade command was not updated. Neither was the cleanup and post-hook callbacks in confd! So when a container had been added to the system, the cleanup callback just simply deleted the script, preventing it from being recreated at ugprade This patch fixes the container identification code and also refactors the execd code to ensure that kill scripts (for deleting in background) and start scripts are run in the proper order *and* ensuring that execd also does not accidentally remove the container start script. Some cosmetic changes to the output at upgrade have also been added. Fixes #623 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
troglobit
added a commit
that referenced
this issue
Sep 13, 2024
In 0edc2d5 and afbe5ca, just prior to v24.06.0-rc1, support for deleting containers in the background was added. However, this also broke support for upgrading containers. In afbe5ca the start script for containers was renamed from NAME.sh to S01-NAME.sh, but the container wrapper script's upgrade command was not updated. Neither was the cleanup and post-hook callbacks in confd! So when a container had been added to the system, the cleanup callback just simply deleted the script, preventing it from being recreated at ugprade This patch fixes the container identification code and also refactors the execd code to ensure that kill scripts (for deleting in background) and start scripts are run in the proper order *and* ensuring that execd also does not accidentally remove the container start script. Some cosmetic changes to the output at upgrade have also been added. Fixes #623 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
troglobit
added a commit
that referenced
this issue
Sep 13, 2024
In 0edc2d5 and afbe5ca, just prior to v24.06.0-rc1, support for deleting containers in the background was added. However, this also broke support for upgrading containers. In afbe5ca the start script for containers was renamed from NAME.sh to S01-NAME.sh, but the container wrapper script's upgrade command was not updated. Neither was the cleanup and post-hook callbacks in confd! So when a container had been added to the system, the cleanup callback just simply deleted the script, preventing it from being recreated at ugprade This patch fixes the container identification code and also refactors the execd code to ensure that kill scripts (for deleting in background) and start scripts are run in the proper order *and* ensuring that execd also does not accidentally remove the container start script. Some cosmetic changes to the output at upgrade have also been added. Fixes #623 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
troglobit
added a commit
that referenced
this issue
Sep 13, 2024
In 0edc2d5 and afbe5ca, just prior to v24.06.0-rc1, support for deleting containers in the background was added. However, this also broke support for upgrading containers. In afbe5ca the start script for containers was renamed from NAME.sh to S01-NAME.sh, but the container wrapper script's upgrade command was not updated. Neither was the cleanup and post-hook callbacks in confd! So when a container had been added to the system, the cleanup callback just simply deleted the script, preventing it from being recreated at ugprade This patch fixes the container identification code and also refactors the execd code to ensure that kill scripts (for deleting in background) and start scripts are run in the proper order *and* ensuring that execd also does not accidentally remove the container start script. Some cosmetic changes to the output at upgrade have also been added. Fixes #623 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
troglobit
added a commit
that referenced
this issue
Sep 13, 2024
In 0edc2d5 and afbe5ca, just prior to v24.06.0-rc1, support for deleting containers in the background was added. However, this also broke support for upgrading containers. In afbe5ca the start script for containers was renamed from NAME.sh to S01-NAME.sh, but the container wrapper script's upgrade command was not updated. Neither was the cleanup and post-hook callbacks in confd! So when a container had been added to the system, the cleanup callback just simply deleted the script, preventing it from being recreated at ugprade This patch fixes the container identification code and also refactors the execd code to ensure that kill scripts (for deleting in background) and start scripts are run in the proper order *and* ensuring that execd also does not accidentally remove the container start script. Some cosmetic changes to the output at upgrade have also been added. Fixes #623 Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since Infix v24.06 the command
container upgrade NAME
, as described in the documentation, no longer works:The text was updated successfully, but these errors were encountered: