-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Docker swarm and links #50
Comments
so we have multiple different containers for database and frappe itself. we use links to resolve inter container dependencies. I am unsure if it works without linking though. Have you tried (not in the swarm) that it works without links? |
Frappe refuses to finish the GUI setup, without links. What inter-container dependencies? |
the databases are in different containers than Frappe, so they're an inter-container dependencies for the Frappe container. |
That i figured, but what are the actual dependencies? Maybe there are work-arounds, something? |
I am unsure, best is to let it be I guess? I will figure something out over the weekend. |
Cool. If I get a chance too, I'll look into it too. |
I think it's only needed for configuring what the ip for redis and MySQL is on. Which can be replaced by a defined network. |
Hi, you should check out this yml file, I using my own erpnext image but with a little tweak it should works with official docker image too. https://github.com/pipech/erpnext-docker-debian/blob/master/production_setup/prd.yml |
@pipech thanks for that, I see quite a few things that I'll take from your yml and add to mine. |
As of right now, the current compose file doesn't work too well with docker swarm for a few reasons, mainly because it uses Compose File Version 2, not Version 3, and because it uses links. I have tried removing the links, but then frappe keeps crashing during setup. Does someone know what we need links for?
The text was updated successfully, but these errors were encountered: