Fedora 31 Workstation
I am running mysql in a container using podman. After some experimenting I got it running with this command:
podman run --detach --userns=keep-id \ --security-opt label=disable \ --name=mysql \ --env="MYSQL_ROOT_PASSWORD=mysql" --publish 3306:3306 \ --volume=/home/simon/servers/mysql/var/lib/mysql:/var/lib/mysql mysql:8.0 \ --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci \ --lower_case_table_names=1
The bits that took time to research were: --userns=keep-id - which maps my user to the same uid in the container --security-opt label=disable - which disables SELinux in the container (dev machine so OK)
I could then connect to the database using the mysql client:
mysql -u root -p -h 127.0.0.1 -P 3306
Now, after a dnf upgrade this has stopped working and I get an error message:
ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (111)
The container is running and appears to be healthy. I've tried recreating the container and reinitialising the database (by deleting all the files).
[simon@hedgehog ~]$ podman ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d7ee24d35a93 docker.io/library/mysql:8.0 --character-s 12 minutes ago Up 12 minutes ago 0.0.0.0:3306->3306/tcp mysql
Podman was updated during the upgrade, as was the kernel and a bunch of other stuff.
simon@hedgehog ~]$ dnf history info 70 | grep podman Upgrade podman-2:1.8.0-2.fc31.x86_64 @updates Upgraded podman-2:1.7.0-2.fc31.x86_64 @@System Upgrade podman-plugins-2:1.8.0-2.fc31.x86_64 @updates Upgraded podman-plugins-2:1.7.0-2.fc31.x86_64 @@System
Does anyone have any idea how I can get this working again? Or any clues as to how I should go about investigating further?
Thanks,
Simon
On 2/17/20 2:49 PM, Simon Colston wrote:
Fedora 31 Workstation
I am running mysql in a container using podman. After some experimenting I got it running with this command:
podman run --detach --userns=keep-id \ --security-opt label=disable \ --name=mysql \ --env="MYSQL_ROOT_PASSWORD=mysql" --publish 3306:3306 \ --volume=/home/simon/servers/mysql/var/lib/mysql:/var/lib/mysql mysql:8.0 \
Change this line to
--volume=/home/simon/servers/mysql/var/lib/mysql:/var/lib/mysql:Z mysql:8.0 \
And you won't need to disable SELinux separation.
--character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci \ --lower_case_table_names=1
The bits that took time to research were: --userns=keep-id - which maps my user to the same uid in the container --security-opt label=disable - which disables SELinux in the container (dev machine so OK)
I could then connect to the database using the mysql client:
mysql -u root -p -h 127.0.0.1 -P 3306
Now, after a dnf upgrade this has stopped working and I get an error message:
ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (111)
The container is running and appears to be healthy. I've tried recreating the container and reinitialising the database (by deleting all the files).
[simon@hedgehog ~]$ podman ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d7ee24d35a93 docker.io/library/mysql:8.0 --character-s 12 minutes ago Up 12 minutes ago 0.0.0.0:3306->3306/tcp mysql
Podman was updated during the upgrade, as was the kernel and a bunch of other stuff.
simon@hedgehog ~]$ dnf history info 70 | grep podman Upgrade podman-2:1.8.0-2.fc31.x86_64 @updates Upgraded podman-2:1.7.0-2.fc31.x86_64 @@System Upgrade podman-plugins-2:1.8.0-2.fc31.x86_64 @updates Upgraded podman-plugins-2:1.7.0-2.fc31.x86_64 @@System
Does anyone have any idea how I can get this working again? Or any clues as to how I should go about investigating further?
Thanks,
Simon _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 17/02/2020 19:56, Daniel Walsh wrote:
On 2/17/20 2:49 PM, Simon Colston wrote:
Fedora 31 Workstation
I am running mysql in a container using podman. After some experimenting I got it running with this command:
podman run --detach --userns=keep-id \ --security-opt label=disable \ --name=mysql \ --env="MYSQL_ROOT_PASSWORD=mysql" --publish 3306:3306 \ --volume=/home/simon/servers/mysql/var/lib/mysql:/var/lib/mysql mysql:8.0 \
Change this line to
--volume=/home/simon/servers/mysql/var/lib/mysql:/var/lib/mysql:Z mysql:8.0 \
And you won't need to disable SELinux separation.
Thanks. I've put that in but still can't connect with mysql client.
Simon
On 2/17/20 3:17 PM, Simon Colston wrote:
On 17/02/2020 19:56, Daniel Walsh wrote:
On 2/17/20 2:49 PM, Simon Colston wrote:
Fedora 31 Workstation
I am running mysql in a container using podman. After some experimenting I got it running with this command:
podman run --detach --userns=keep-id \ --security-opt label=disable \ --name=mysql \ --env="MYSQL_ROOT_PASSWORD=mysql" --publish 3306:3306 \ --volume=/home/simon/servers/mysql/var/lib/mysql:/var/lib/mysql mysql:8.0 \
Change this line to
--volume=/home/simon/servers/mysql/var/lib/mysql:/var/lib/mysql:Z mysql:8.0 \
And you won't need to disable SELinux separation.
Thanks. I've put that in but still can't connect with mysql client.
Simon _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
What error are you seeing? What AVCs?
On 18/02/2020 18:37, Daniel Walsh wrote:
On 2/17/20 3:17 PM, Simon Colston wrote:
On 17/02/2020 19:56, Daniel Walsh wrote:
On 2/17/20 2:49 PM, Simon Colston wrote:
Fedora 31 Workstation
I am running mysql in a container using podman. After some experimenting I got it running with this command:
podman run --detach --userns=keep-id \ --security-opt label=disable \ --name=mysql \ --env="MYSQL_ROOT_PASSWORD=mysql" --publish 3306:3306 \ --volume=/home/simon/servers/mysql/var/lib/mysql:/var/lib/mysql mysql:8.0 \
What error are you seeing? What AVCs?
Thanks, but I'm not seeing any errors or AVCs.
I've done some more investigation and I have a reproduction recipe. If I run with this command
podman run --userns=keep-id \ --name=mysql \ --env="MYSQL_ROOT_PASSWORD=mysql" --publish 3306:3306 \ --volume=/home/simon/servers/mysql/var/lib/mysql:/var/lib/mysql:Z mysql:8.0
I can connect with the mysql client with no errors.
mysql -u root -p -h 127.0.0.1 -P 3306 Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. etc.
If I then do:
podman stop mysql podman start mysql
then I can no longer connect with the mysql client.
mysql -u root -p -h 127.0.0.1 -P 3306 Enter password: ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (111)
I then reset everything: podman stop mysql podman rm mysql and delete all the database files.
If I remove the --userns=keep-id argument I can connect after a 'stop' and a 'start'. (Except that the database files now have an odd user id that I can only delete as root)
So, I think the --userns=keep-id is the problem and it fails after restarts.
So am I doing something wrong? This was working fine before the upgrade from podman 1.7 to 1.8
Simon
On 2/18/20 4:20 PM, Simon Colston wrote:
On 18/02/2020 18:37, Daniel Walsh wrote:
On 2/17/20 3:17 PM, Simon Colston wrote:
On 17/02/2020 19:56, Daniel Walsh wrote:
On 2/17/20 2:49 PM, Simon Colston wrote:
Fedora 31 Workstation
I am running mysql in a container using podman. After some experimenting I got it running with this command:
podman run --detach --userns=keep-id \ --security-opt label=disable \ --name=mysql \ --env="MYSQL_ROOT_PASSWORD=mysql" --publish 3306:3306 \ --volume=/home/simon/servers/mysql/var/lib/mysql:/var/lib/mysql mysql:8.0 \
What error are you seeing? What AVCs?
Thanks, but I'm not seeing any errors or AVCs.
I've done some more investigation and I have a reproduction recipe. If I run with this command
podman run --userns=keep-id \ --name=mysql \ --env="MYSQL_ROOT_PASSWORD=mysql" --publish 3306:3306 \ --volume=/home/simon/servers/mysql/var/lib/mysql:/var/lib/mysql:Z mysql:8.0
I can connect with the mysql client with no errors.
mysql -u root -p -h 127.0.0.1 -P 3306 Enter password: Welcome to the MySQL monitor. Commands end with ; or \g. etc.
If I then do:
podman stop mysql podman start mysql
then I can no longer connect with the mysql client.
mysql -u root -p -h 127.0.0.1 -P 3306 Enter password: ERROR 2003 (HY000): Can't connect to MySQL server on '127.0.0.1' (111)
I then reset everything: podman stop mysql podman rm mysql and delete all the database files.
If I remove the --userns=keep-id argument I can connect after a 'stop' and a 'start'. (Except that the database files now have an odd user id that I can only delete as root)
So, I think the --userns=keep-id is the problem and it fails after restarts.
So am I doing something wrong? This was working fine before the upgrade from podman 1.7 to 1.8
Simon
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Seems like it could be something with slirp4netns?
Giuseppe any ideas?
-
Daniel Walsh -
Simon Colston