Skip to content
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 start and ready order enforcement #3

Open
ML-TANGO opened this issue Sep 7, 2022 · 1 comment
Open

container start and ready order enforcement #3

ML-TANGO opened this issue Sep 7, 2022 · 1 comment
Assignees
Labels
bug Something isn't working invalid This doesn't seem right

Comments

@ML-TANGO
Copy link
Owner

ML-TANGO commented Sep 7, 2022

Using docker-compose.yaml and docker-compose command, we can start order of two or more containers, but it does not guarantee the readiness of the dependent container prior to start next container.

Followings are stackoverflow articles related to this issue:

@ML-TANGO ML-TANGO assigned ML-TANGO, hongsoog and choijinpyo and unassigned ML-TANGO Sep 7, 2022
@ML-TANGO ML-TANGO added bug Something isn't working invalid This doesn't seem right labels Sep 7, 2022
@ML-TANGO
Copy link
Owner Author

If project manager does not work, please use following process for temporary solution.
The main reason is the dependent postgresql service container is running but not in readiness when the project_manager service contianer starts.

# check all continers list
$ docker ps -a 

# if some container got into problem such as EXIT or RESTART, please down all TANGO containers
$ docker-compose down

# and restart all the componets 
$ docker-compose up -d 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working invalid This doesn't seem right
Projects
Status: Done
Development

No branches or pull requests

3 participants