-
Notifications
You must be signed in to change notification settings - Fork 57
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
Problem with DB initialization #75
Comments
After manual command execution in mysql container (from Line 74 in e347c20
Line 86 in e347c20
It seems that commands with ${INITIALIZE_DB} = 1 are not optimal in case of 2 separated containers. |
Hrmm most of my installations are using multiple containers and I have not seen this. Looking at those logs it does not install the
Can you verify this is the case here? Running the commands manually is a bit odd, as they should error out with access denied unless the MySQL root password was different between runs. If this is via docker-compose mind sharing so I can attempt to reproduce locally? |
I use Kubernetes (not docker-compose). I have tried to delete all conatainers 3 times. And have the same issue. There is no problem, when mysql and cacti containers are in the same namespace of Kubernetes. But there is a problem, when namespaces are different. |
But there is an access to MySQL from this container:
The text was updated successfully, but these errors were encountered: