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.

Sign up for GitHub

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

Jump to bottom

🐛 : iSeg app/web are not in the same docker network #3261

Closed
mrnicegyu11 opened this issue Aug 15, 2022 · 3 comments
Closed

🐛 : iSeg app/web are not in the same docker network #3261

mrnicegyu11 opened this issue Aug 15, 2022 · 3 comments
Assignees
@GitHK
Labels
bug buggy, it does not work as expected
Milestone
Brutalism

Comments

@mrnicegyu11
Copy link
Member

iSeg fails to start, because the app and web container have slightly differently named docker networks.

It seems that the ___backup__ suffix is missing from one of them.

This might be a concurrency issue.

It is reproducible locally and on prod-deployments
@mrnicegyu11 mrnicegyu11 added the bug buggy, it does not work as expected label Aug 15, 2022
@sanderegg sanderegg added this to the Brutalism milestone Aug 15, 2022
@sanderegg sanderegg mentioned this issue Aug 15, 2022
Open
@sanderegg sanderegg mentioned this issue Aug 23, 2022
Merged
@GitHK
Copy link
Contributor

GitHK commented Sep 6, 2022

@mrnicegyu11 Is this one still there now? Could you check. Not sure if the above PR was released to prod-deployments

@mrnicegyu11
Copy link
Member Author

@GitHK I checked, it is not in prod it is in staging_brutalism5 atm

@mrnicegyu11
Copy link
Member Author

fixed in staging_brutalism5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@GitHK GitHK

Labels
bug buggy, it does not work as expected
Projects
None yet
Milestone
Brutalism
Development

No branches or pull requests
3 participants
@GitHK @mrnicegyu11 @sanderegg