You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2019. It is now read-only.
When I run sudo systemctl stop docker-mariadb-galera I get an error:
Mar 08 23:51:48 cluster1 systemd[1]: Stopping MariaDB with Galera Cluster...
Mar 08 23:51:48 cluster1 bash[23455]: Error response from daemon: No such container: mariadb-container-
This appears to be because in the ExecStop command that parses out a value for HOSTNUM, the variable substitution (with an empty value) happens before the parsing actually occurs.
The container still gets stopped on my machine; I think the ExecStop command probably isn't necessary at all. The docker command inside docker-mariadb-galera.sh runs in the foreground (no -d argument), so systemd is able to send it signals, and that causes docker to shut down the container.
The text was updated successfully, but these errors were encountered:
I cannot reproduce the issue when running the VMs on Azure. Are you using the ARM template for Azure, or are you just using the cloud-config? What distribution are you using - CoreOS?
When I run
sudo systemctl stop docker-mariadb-galera
I get an error:This appears to be because in the
ExecStop
command that parses out a value forHOSTNUM
, the variable substitution (with an empty value) happens before the parsing actually occurs.The container still gets stopped on my machine; I think the
ExecStop
command probably isn't necessary at all. The docker command insidedocker-mariadb-galera.sh
runs in the foreground (no-d
argument), so systemd is able to send it signals, and that causes docker to shut down the container.The text was updated successfully, but these errors were encountered: