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

MySQL database needs to be initialized manually if containers are restarted #1

Closed
bakhtos opened this issue May 28, 2024 · 2 comments
Closed
Labels
deployment Issues related to deployment of docker and locust of the system

Comments

@bakhtos
Copy link
Collaborator

bakhtos commented May 28, 2024

For some reason, the mysql container does not automatically read the file put into it during deployment, even though it is supposed to according to documentation.

Restarting the containers also requires logging into the mysql container and manually piping the file into mysql process.

@bakhtos bakhtos added the deployment Issues related to deployment of docker and locust of the system label May 28, 2024
@bakhtos
Copy link
Collaborator Author

bakhtos commented May 28, 2024

Potential fix could be specifying which user should be used in the container in the docker-composefile and fixing permissions of the .sql file on the host

@bakhtos bakhtos changed the title MySQLdatabase needs to be initialized manually if containers are restarted MySQL database needs to be initialized manually if containers are restarted May 28, 2024
@bakhtos
Copy link
Collaborator Author

bakhtos commented May 30, 2024

Fixed with a command that waits for the container to boot up and read the sql file

@bakhtos bakhtos closed this as completed May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployment Issues related to deployment of docker and locust of the system
Projects
None yet
Development

No branches or pull requests

1 participant