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?

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

Well, it says data is not running… Try running this: ./launcher rebuild data ./launcher rebuild web_only

[תמונה] riking: Well, it says data is not running… Try running this: 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.

לא ניתן לקשר לקונטיינר שאינו פועל: /data AS /web_only/data

תמיכה

riking (Kane York) 10 בספטמבר,‏ 2020,‏ 2:18am 4

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

נושא		תגובות	צפיות
Failed to bootstrap web_only - no cid file but totally fresh build Self-hosting two-container	2	891	6 באפריל,‏ 2018
Docker: Error response from daemon: Could not get container for data Self-hosting	4	6545	27 ביוני,‏ 2017
Suddenly I'm not able to bootstrap 'Data' container Self-hosting two-container	1	152	12 באוגוסט,‏ 2024
Re-bootstrap data container in a split setup? Product Support	4	1314	29 באפריל,‏ 2015
Bootstrapping failing for data.yml as well as web_only Self-hosting two-container	2	485	28 בפברואר,‏ 2024

לא ניתן לקשר לקונטיינר שאינו פועל: /data AS /web_only/data

נושאים קשורים