I dug a bit deeper and it turned out the problem here is caused by port 3306 already being occupied by another local test-container and therefore mysqld aborting on startup.
So in the end, the problem could be reduced to: when mysqld fails to start (as defined in ExecStart=), the 'mysqladmin ping' loop should behave a bit more intelligent instead of pinging to nowhere. If it is doable, backporting the systemd related improvements in MySQL [1] would solve this problem and also get rid of all those hacks to make MySQL 5.6 work with systemd. [1] http://mysqlserverteam.com/mysql-5-7-native-systemd-support/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1478849 Title: infinite loop in /usr/share/mysql/mysql-systemd-start causes non- interactive installations to fail/hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1478849/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
