This repository was archived by the owner on May 6, 2025. It is now read-only.
Only run entry point scripts when the container first starts #10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
There is a difference between volker down and volker stop, down also deletes the containers.
Right now when you do volker stop and then volker up, the initial entrypoint scripts are run again - reinstalling and setting up things afresh.
I think we should only do this the first time so you need to volker down and volker up to re-run the entrypoint scripts installs.
This will enable the volker stop -> volker up to be a must faster restart mechanism
Tested the changes locally, here's the log