-
Notifications
You must be signed in to change notification settings - Fork 137
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
Starting MariaDB database server: mysqld failed #168
Comments
Hi @aristosv Can you add a new volume for /var/log/mysql and see what the error is? |
So I followed your suggestion and added the volume, like this
and under /var/log/mysql I found these files But these files also exist in the root configuration folder of the container That's not right, is it? In fact, any volume I browse within the container, I get the same files So it would make sense for mariadb not to be able to start, if it's path is the same as every other path in the container. My guess it's something wrong with the way the container is build, it doesn't really allow persistent storage? I checked my other containers volumes and each volume has it's own directory within the container. I hope this helps. |
Hi @aristosv Thanks for trying it. I had missed one small detail in your docker run command earlier. You need to give separate directories for each of the volumes. So something like:
|
Thanks for you reply. I'm no docker expert, but this is what I have so far with all my other containers On the left side of the : I always use the name of the container, which points to /var/lib/docker/volumes/$containername/_data. And on the right side of the : I always put the paths of the volumes created by the container. This way the container can use /var/lib/docker/volumes/$containername/_data to create it's directory structure, as it sees fit. This is what I do with all my containers, and they all use that path. So far I never had to manually create directory paths on the left side of the : But I did try the command you recommended, and this is the error I got.
|
Hi @aristosv I think the problem is that when you start it the original way, docker is not creating the subdirectories and dumping everything under the rundeck directory. I haven't seen this happen before. I usually specify my volume directories so I can point it to an exact location. Can you try testing with an exact path on the left side? |
When I specify an exact path on the left side (including separate directories) it works. It's the first time I had to do something like this though. This is how I usually install my containers. I'm assuming it's something that's defined in the Dockerfile?
|
I'll have to take a look. I started the container when docker was still in beta and haven't had anyone mention the issue before. Maybe there's something new that needs to be added as you mentioned 😞 |
Hello,
I am using this command to set up rundeck in a container.
This is what I get in the log files
And it keeps looping like this.
I'm I doing something wrong?
Thanks
The text was updated successfully, but these errors were encountered: