I have restarted the rancher host a few times while configuring rancher.

Nothing was lost, even though containers had been started and stopped several times during these reboots.

I had to stop and run the container again to set a specific IP for the UI, so I could use the other IP addresses available in the host as HostPorts for containers.

This is the command I had to execute again:

docker run -d --restart=unless-stopped -p 1.2.3.4:80:80 -p 1.2.3.4:443:443 rancher/rancher

After running this, rancher started up as a clean installation, asking me for password, to setup a cluster, and do everything from scratch, even though I see a lot of containers running.

I tried rerunning the command that rancher showed on the first installation (including the old token and ca-checksum). Still nothing.

Why is this happening? Is there a way to restore the data, or should I do the configuration and container creation again?

What is the proper way of cleaning up, if I need to start from scratch? docker rm all containers and do the setup again?

UPDATE

I just found some information from another member in a related question, because this problem happened following a suggestion from another user.

Apparently there is an upgrade process that needs to be followed, but I am missing what needs to be done exactly. I can see my old, stopped container here: https://snag.gy/h2sSpH.jpg

I believe I need to do something with that container so the new rancher container becomes online with the previous data.

Should I be running this?

docker run -d --volumes-from stoic_newton --restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher:latest