NAS-130199 / 24.10 / Make sure docker networks get recreated with compose up action #14070
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
When we have a running app and system is rebooted, any docker networks which might have been created don't have their associated interfaces anymore present after the reboot. So if an attempt to start the app is made, what happens is that process fails. For starting the app
docker compose up --force-recreate
is used, however this does not re-create the docker networks and eventually the interfaces as well which are associated with it. It fails with something likeSolution
We make sure whenever compose up action is desired, any networks in place are removed first for the app so that the app can safely start.