Bind mounted database for rancher server

Archive Rancher 1.x
1

This might be a bit silly and I might just be a bit slow today, but I was trying to move my mysql data out of the rancher/server container and bind mount it. On boot, upgrading to latest, now I am receiving:

151119 20:13:25 [Note] /usr/sbin/mysqld (mysqld 5.5.44-0ubuntu0.14.04.1-log) starting as process 23 …
151119 20:13:32 [Note] /usr/sbin/mysqld (mysqld 5.5.44-0ubuntu0.14.04.1-log) starting as process 25 …
151119 20:13:45 [Note] /usr/sbin/mysqld (mysqld 5.5.44-0ubuntu0.14.04.1-log) starting as process 24 …
s6-svscanctl: fatal: unable to control /service: supervisor not listening

I am starting to wonder if I am getting the host-side permissions wrong on the mysql data, but I don’t know what uid/gid it would expect internally – assuming this is even the issue.

Any ideas?

2

Discovered the problem.

IF you decide to bind mount your database during POC/testing/etc etc.
Chown your host-side data dir to 102:105 which is the uid/gid of the mysql user inside the container.

ccorbett@pompeii:/var/tmp$ sudo chown -R 102:105 mysql/

Now I finally get to play with the latest rancher server :dizzy_face:

Rancher admins: you can lock/close this.