Cannot link to a non running container: /data AS /web_only/data

We’ve just dated from version 4.2 to the latest version.
We run a data container and web container.
Now discourse is not booting with the following error.

[root@sydney discourse]# ./launcher start web_only

starting up existing container
+ /bin/docker start web_only
Error response from daemon: Cannot link to a non running container: /data AS /web_only/data
Error: failed to start containers: web_only

Any ideas on how to resolve this?

Well, it says data is not running… Try running this:

./launcher rebuild data
./launcher rebuild web_only

data is running.

[root@sydney discourse]# docker ps | grep data
860547699a11        local_discourse/data            "/sbin/boot"             2 hours ago         Up 2 hours     

Maybe renaming the reference in the docker image from local_discourse/data to web_only/data would cut it.

In that case, re-check all references to data from the web_only.yml file.

I think this happens if you rebuild the data container and start up a new one. Even though it’s still named data, the running web container is still looking for the old one. I think this should do it:

./launcher stop web_only
./launcher destroy web_only
./launcher start web_only

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.