Problems with run docker image

[yapro]

docker run -d --net=host --name=pinba tony2001/pinba

check:

docker ps
CONTAINER ID        IMAGE                         COMMAND                  CREATED             STATUS              PORTS                                                                                                NAMES
a99ad76e0309        tony2001/pinba                "/local/mysql/bin/env"   8 seconds ago       Up 8 seconds                                                                                                             pinba

and check again:

docker ps -a
CONTAINER ID        IMAGE                         COMMAND                  CREATED             STATUS                         PORTS                                                                                                NAMES
65d5e1c0896b        tony2001/pinba                "/local/mysql/bin/env"   12 minutes ago      Exited (1) 4 minutes ago                                                                                                            jolly_goldberg

Checking whats wrong:

docker logs pinba
2016-06-10 17:27:46 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-06-10 17:27:46 0 [Note] /local/mysql/bin/mysqld (mysqld 5.6.30) starting as process 1 ...

Do you have any ideas?

[pmontepagano]

I had two issues with the Docker image, maybe you have some of them:

1. It need's at least 2GB of RAM. I was trying on a micro instance in AWS (1GB), so OOM killer would kill my instance.

2. I had MySQL running on my docker host, so the 3306 port was already bound by another process.

[fe3dback]

confirm this

Free mem: 10GB

Linux ln 4.10.0-35-generic #39~16.04.1-Ubuntu SMP Wed Sep 13 09:02:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Docker version 17.06.2-ce, build cec0b72

i not have mysql working on localhost.

[g3rhard]

@yapro
Confirm this message #53 (comment)
On my test machine, it was also necessary to add a swap file of at least 2 GB, because after launching the pinba, the free space in the swap decreased by 1.5GB.
And yes, when other process bound ports 3306 or 30002 pinba won't start.

[gggeek]

About the issue with other processes occupying ports 3306 or 30002: it is relatively easy to add a -p switch to the command line used to start the Pinba container, so that the ports it listens to get mapped to different ports on the host. I agree this could be documented somewhere a bit better.