To add more context:
For below issue, can you just try to remove the etcd image and do the re-provision again?
You can remove the image by using below command
$ dokcer rmi -f <image>
after done cleaning up the etcd image, you can run the step for provisioning again.
Let me know if this method is working for you.
Hi, I've removed this images with the indicated command, but I still can see a process taken the port 2379.
# docker images
ia_etcd_provision 2.3 376fb81c0989 3 days ago 194MB
ia_etcd 2.3 f0c451c6fc74 3 days ago 181MB
# dokcer rmi -f 376fb81c0989
# dokcer rmi -f f0c451c6fc74
On the other hand, there is no Docker container running.
Actually, if I am not mistaken, you have ETCD ports taken even when there are no Docker containers running, implying the ETCD service is run from the host OS. Can you double check?
If this is the case, please make sure that by stopping this ETCD instance, it doesn't break what's already running and depending on this ETCD cluster. If you are not sure, you might want to find another device that's clean to set up EII (Edge Insights for Industrial, previously known as EIS).
Hi, I think this is the case because I can't see a running Docker container. The point is that I don't know how to stop this ETCD instance. I locate the process id and killed it, but its created with a new process id, taking the port 2379 again:
# sudo lsof -i -P -n | grep etcd
# sudo kill -9 8339
Hi all, this is the workaround I found to stabilize EIS (all Docker containers UP) every time I reboot the computer and got the reported issue.
docker-compose down ps axf | grep etcd -B 5 sudo kill -9 <./start_etcd.sh PID> systemctl restart docker.service xhost + sudo ./provision_eis.sh ../docker-compose.yml docker-compose up --build -d
From the situation that you mentioned below, you already can get all the container up and running after you reboot the system may I know what is running?
If you already run the container, after rebooting the system all the containers should be running you will only need to run the xhost + command for the visualizer.
can you help to give a list of docker containers that run before and after rebooting the system?
If you do "systemctl | grep etcd" from the host, do you see any entry? If there is one and you are sure this ETCD instance isn't used for anything, you can use "systemctl stop [servicename]" and "systemctl disable [servicename]" to stop it from running in the future.
As mentioned in the user guide and read me. The xhost + command need to be rerun everytime after rebooting the system because this is needed by
ia_visualizer service to render the UI.
May I know what will be the behaviour if you just running this command after rebooting without doing systemctl restart docker.service command ?