You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running this two times (to create two individual WordPress Dockers on a host machine) will lead to a conflicting database (due to the static volume and DB name)?
#39
Open
Dzhuneyt opened this issue
Jun 18, 2015
· 1 comment
I noticed that you are mounting the mysql volume and always creating a DB named "wordpress" when this DockerFile is runned. What if I decide to run multiple WordPress installations with separate Dockers on a same host?
They will confluct due to the same DB name in my opinion - "wordpress".
The easiest solution would be to randomize the DB name based on a timestamp or some other mechanism to avoid conflicting names.
The text was updated successfully, but these errors were encountered:
No. You should mount different host volumes into the containers. One uniquely for one container instance. Or just not even mount anything into the container. Having multiple mysql daemons work on the same files will most likely destroy your dbs.
I noticed that you are mounting the mysql volume and always creating a DB named "wordpress" when this DockerFile is runned. What if I decide to run multiple WordPress installations with separate Dockers on a same host?
They will confluct due to the same DB name in my opinion - "wordpress".
The easiest solution would be to randomize the DB name based on a timestamp or some other mechanism to avoid conflicting names.
The text was updated successfully, but these errors were encountered: