Update Rancher. Question

Archive Rancher 1.x
1

Guys, you’ll probably laugh, but I have a question about the update:
1.

 $ docker stop <container_name_of_original_server>

<container_name_of_original_server> - what is my name container?

I installed as all
sudo docker run -d --restart=always -p 8080:8080 rancher/server
2.

$ docker create --volumes-from <container_name_of_original_server> --name rancher-data rancher/server:<tag_of_previous_rancher_server>

<tag_of_previous_rancher_server> - what is my tag of previous rancher server?

$ docker cp <container_name_of_original_server>:/var/lib/mysql <path on host>

- for example, or which may be a standard?

Thank you for understanding, for many it may not even a question, but for me it is a problem.

2
  1. docker ps - will list your containers and you can see the name of the rancher server in the last column
  2. docker images - second column - tag of previous server - refers to the version of the previous rancher server eg: v0.32.0
  3. see point 1, this will give you the unique docker name of the previous rancher server , the only standard being it would be a two fold name eg: grumpy_wombat
3

which path on host-?

4

that is entirely up to you.
/home/
/tmp
/opt/data/

This choice is yours where you want to keep the exported data.

5 
$ docker stop goofy_brown
$ docker cp goofy_brown:/var/lib/mysql :/home/
$ docker run -d -v :/home/ :/var/lib/mysql -p 8080:8080 --restart=always rancher/server:latest

is it right?

6

almost, try below
docker cp goofy_brown:/var/lib/mysql /home/
docker run -d -v /home/:/var/lib/mysql -p 8080:8080 --restart=always rancher/server:latest

7

thanks, I did, but did not start Rancher

8

please provide output of: docker ps -a

9

Screenshot_1.png1350×130 13.1 KB

10

ok, my thinking is that one rancher server container there, with the created status might be the issue.
however, since you have the mysql data now to a local folder. (assuming)

you could try clearing all other containers and starting just the rancher server one.

Try these commands, note, this will remove all containers running and stopped.

docker stop $(docker ps -aq) && docker rm $(docker ps -aq)

after that, try running the command again to start the Rancher server.

11

Screenshot_2.png1339×242 16.4 KB

I did, but did not start Rancher

12

Screenshot_3.png1348×63 6 KB

13

output of: docker logs <container_name>

wondering if not a conflict somewhere along the line.
Age old support question…have you rebooted/restart your server? :stuck_out_tongue:

14

Screenshot_5.png899×641 84.2 KB

15

It starts from scratch:

sudo docker run -d --restart=always -p 8080:8080 rancher/server

but it does not run dump database:

docker run -d -v /home/:/var/lib/mysql -p 8080:8080 --restart=always rancher/server:latest