The container launches multiple mysqld processes in a loop

[onnimonni]

I have multiple problems when mapping this to another port than the default 3306. I'm using the 3307 port instead.
When I do this container starts multiple processes and won't allow logging in.
$ mysql -u super --password=J8s0hY0d6QJsOfF0 --protocol=tcp --port=3307
ERROR 2013 (HY000): Lost connection to MySQL server at 'reading initial communication packet', system error: 0

[Painted-Fox]

Yes, you certainly can. When you run the container try adding this flag: -p 3307:3306. This means the container's port 3306 will be exposed on the host's 3307 port. There's mor information on this in Docker's documentation section on exposing incoming ports.

Is this what you mean? It's more difficult to change the port the container will use internally.

[onnimonni]

Yeah I figured that out, thanks. What about the multiple mysqld processes this launches? I think there's some bug in my instance and it starts the mysqld process in loop.

$ sudo docker run -d -name="mariadb" \
>              -p 127.0.0.1:3306:3306 \
>              -v /tmp/mariadb:/data \
>              -e USER="super" \
>              -e PASS="$(pwgen -s -1 16)" \
>              paintedfox/mariadb
Warning: '-name' is deprecated, it will be replaced by '--name' soon. See usage.
c11ccb25864ad8b1e577438ca1defe3c39290d3dac1bc6e82054c53aab1689d9
 $ sudo docker logs mariadb
*** Running /etc/rc.local...
*** Booting runit daemon...
*** Runit started as PID 10
MARIADB_USER=super
MARIADB_PASS=rAMioE88zEw1uFS4
MARIADB_DATA_DIR=/data
Starting MariaDB...
140521 14:42:09 mysqld_safe Logging to syslog.
140521 14:42:09 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140521 14:42:09 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
MARIADB_USER=super
MARIADB_PASS=rAMioE88zEw1uFS4
MARIADB_DATA_DIR=/data
Starting MariaDB...
140521 14:42:10 mysqld_safe Logging to syslog.
140521 14:42:10 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140521 14:42:10 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
MARIADB_USER=super
MARIADB_PASS=rAMioE88zEw1uFS4
MARIADB_DATA_DIR=/data
Starting MariaDB...
140521 14:42:12 mysqld_safe Logging to syslog.
140521 14:42:12 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140521 14:42:12 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
MARIADB_USER=super
MARIADB_PASS=rAMioE88zEw1uFS4
MARIADB_DATA_DIR=/data
Starting MariaDB...
140521 14:42:13 mysqld_safe Logging to syslog.
140521 14:42:13 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140521 14:42:14 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
MARIADB_USER=super
MARIADB_PASS=rAMioE88zEw1uFS4
MARIADB_DATA_DIR=/data
Starting MariaDB...
140521 14:42:15 mysqld_safe Logging to syslog.
140521 14:42:15 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140521 14:42:15 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
MARIADB_USER=super
MARIADB_PASS=rAMioE88zEw1uFS4
MARIADB_DATA_DIR=/data
Starting MariaDB...
140521 14:42:17 mysqld_safe Logging to syslog.
140521 14:42:17 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140521 14:42:17 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
MARIADB_USER=super
MARIADB_PASS=rAMioE88zEw1uFS4
MARIADB_DATA_DIR=/data
Starting MariaDB...
140521 14:42:18 mysqld_safe Logging to syslog.
140521 14:42:18 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140521 14:42:18 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
MARIADB_USER=super
MARIADB_PASS=rAMioE88zEw1uFS4
MARIADB_DATA_DIR=/data
Starting MariaDB...
140521 14:42:20 mysqld_safe Logging to syslog.
140521 14:42:20 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140521 14:42:20 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
MARIADB_USER=super
MARIADB_PASS=rAMioE88zEw1uFS4
MARIADB_DATA_DIR=/data
Starting MariaDB...
140521 14:42:21 mysqld_safe Logging to syslog.
140521 14:42:22 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140521 14:42:22 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
MARIADB_USER=super
MARIADB_PASS=rAMioE88zEw1uFS4
MARIADB_DATA_DIR=/data
Starting MariaDB...
140521 14:42:23 mysqld_safe Logging to syslog.
140521 14:42:23 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
140521 14:42:23 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
MARIADB_USER=super
MARIADB_PASS=rAMioE88zEw1uFS4
MARIADB_DATA_DIR=/data
Starting MariaDB...

[onnimonni]

My version is:

$ sudo docker version
Client version: 0.9.1
Go version (client): go1.2.1
Git commit (client): 3600720
Server version: 0.9.1
Git commit (server): 3600720
Go version (server): go1.2.1
Last stable version: 0.11.1, please update docker

[Painted-Fox]

Oh crud! That's a problem.

[Painted-Fox]

What command are you using to start your container? Would you happen to be using Vagrant?

[onnimonni]

I'm using the command shown in the earlier comment. My system is ubuntu 14.04 and I downloaded the mariadb container image straight from docker index.
Linux kd3 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

[renato-zannon]

I wasn't able to reproduce this (using the very same command) on docker 0.11.1

@onnimonni could you retry with the latest docker? Also, what are the contents of your /tmp/mariadb folder before running the command?

[Painted-Fox]

I was not able to reproduce the server trying to start over and over either.

However, I've found out a likely reason why you weren't able to connect to MariaDB and I fixed this with the latest change I made. Essentially sed was not having an effect on the configuration file after the configuration directory was included in the VOLUME statement. This meant that the container would bind to 127.0.0.1 (the default) and not accept any incoming connections from other sources.

Are you able to upgrade your docker version?

[onnimonni]

I'm not sure how to do that. Ubuntu says latest package is 0.9.1.

I tried with latest docker server binary (0.11) but with earlier docker client (0.9.1). I deleted the files in mariadb directory and started the container again. The results were still the same.
I have been using this container in other servers successfully many times. Strange that this is happening since docker shouldn't be depending on environment

[onnimonni]

Ok I managed to install reinstall docker with the latest but still getting loop error

[Painted-Fox]

Thank you very much for updating docker and verifying that it still happens. I'm unfortunately unable to reproduce the loop error still, however. Could you possibly verify that we've pulled the same image? The latest image id is 3769a588bdac.

fox@Squeak:~/proj/docker-mariadb$ docker images paintedfox/mariadb
REPOSITORY           TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
paintedfox/mariadb   latest              3769a588bdac        19 hours ago        544.6 MB

As far as environment goes, sometimes I've noticed differences when people use Vagrant, but you're right, it shouldn't make a difference. Most of the time I'll check the docker index and see that my Trusted Build failed for some reason, so people are pulling an old version, or that a build from there behaves slightly different from one that I've built myself.

I'm sorry you're experiencing this error. How many servers do you have running paintedfox/mariadb? I'm excited to hear that you're using it.

[zar29]

I am experiencing the same issue, I think it's related to the custom init system the phusion base image uses. I'm on 14.04 with the following docker version: 0.9.1, build 3600720.

I have been using this in production but was foolish enough to update it without testing it thoroughly first, does anyone know how I can fix this?

[Painted-Fox]

I made a change to avoid using runit, the phusion base image's init system for services. If you do a docker pull you should get the change and the image id is 97b9f9cc2abb.

@heyimwill I'm sorry my changes broke your production system. Could you let me know if this fixes the issue?

[richardcrichardc]

I have also had trouble with paintedfox/mariadb on Ubuntu 14.04. I have tried with both Docker 0.9.1 which comes with 14.04 and 0.10 from Docker's Ubuntu repos. This is the error I got:

May 28 00:07:03 4df6c7e6d953 mysqld_safe: Starting mysqld daemon with databases from /data
May 28 00:07:03 4df6c7e6d953 mysqld: 140528  0:07:03 [ERROR] mysqld: File '/var/log/mysql/mariadb-bin.index' not found (Errcode: 13)
May 28 00:07:03 4df6c7e6d953 mysqld: 140528  0:07:03 [ERROR] Aborting

So I tried a different Docker image for (this time for MySQL) and had similar issues. Not sure if it was exactly the same as I could not see where the Mysql log was in the other container.

Finally I have switched to CoreOS from Ubuntu as the Docker host and paintedfox/mariadb just works. So I think this is a Ubuntu problem. I'm looking forward to when Docker has a stable release.