Make a permanent folder

Question

Make a permanent folder

Closed this issue 9 years ago · 40 comments

cedvan commented 9 years ago

Hi,

How make a permanent folder ?

I create an folder /var/lib/rancher with files in VM, after vagrant halt and vagrant up, folder disappeared.

Thank you

Answer 1 · 2016-03-21T23:44:33.000Z

docker-root.box has 40GB HDD and mounts it at /mnt/sda1 (/dev/sda1).
https://github.com/ailispaw/docker-root-packer#dockerroot-packer-for-virtualbox-and-qemu

You can make any folder under the /mnt/sda1 as a persistent one.

Answer 2 · 2016-03-21T23:46:04.000Z

Yes, I already fix my problem, not had time to update issue 😉

Thank you !

Answer 3 · 2016-03-21T23:46:52.000Z

Maybe add information about /mnt/sda1 in Readme.md ?

Answer 4 · 2016-03-21T23:49:41.000Z

I use :

node.vm.provision "shell",
    inline: "rm -f /var/lib/docker && rm -f /var/lib/docker-root && mv /var/lib/* /mnt/sda1/var/lib/ && ln -s /mnt/sda1/var/lib /var/lib"

Because, I can't create symbolic link /var/lib/rancher on provisioning. Docker container want to create it

Answer 5 · 2016-03-21T23:55:03.000Z

Provision is execute only first up. how can I make persistent the symbolic link ?

Answer 6 · 2016-03-21T23:57:19.000Z

Possible add /var overall persistent on docker-root please ?

Would be more clean and logic 😉

Answer 7 · 2016-03-21T23:59:50.000Z

/var/lib/docker && /var/lib/docker-root are reserved by DockerRoot.
Please use as below instead.

  node.vm.provision "shell",
    inline: "mkdir -p /mnt/sda1/var/lib/rancher && \
      rm -f /var/lib/rancher && ln -s /mnt/sda1/var/lib/rancher /var/lib/rancher"

Answer 8 · 2016-03-22T00:01:45.000Z

Impossible sorry, rancher-agent want create /var/lib/rancher. Is /var/lib/rancher exist, failed start 😟

Answer 9 · 2016-03-22T00:02:21.000Z

You can put any scripting into /var/lib/docker-root/start.sh.
https://github.com/ailispaw/docker-root/blob/master/docs/customization.md#customizing-init-scripts-on-booting-up

Or you can use `run: "always" option for a Vagrant provisioner.

Answer 10 · 2016-03-22T00:03:08.000Z

You see rm -f /var/lib/rancher in my script.

Answer 11 · 2016-03-22T00:04:49.000Z

Oh, rancher-agent dose!

Answer 12 · 2016-03-22T00:08:18.000Z

I think rancher-agent should work in that situation.

Answer 13 · 2016-03-22T00:21:31.000Z

Ok for script to make persistent symbolic link with init.d, I'll try, thank you !

But no solution to first start VM. rancher-agent want create /var/lib/rancher on first run, so I can't create symbolic link before run 😢

Answer 14 · 2016-03-22T00:25:19.000Z

You may want to try vagrant-triggers to run it after up.

  if Vagrant.has_plugin?("vagrant-triggers") then
    config.trigger.after [:up, :resume] do
      info "Adjusting datetime after suspend and resume."
      run_remote "sudo sntp -4sSc pool.ntp.org; date"
    end
  end

Answer 15 · 2016-03-22T00:39:37.000Z

It was wrong.

I just got an idea.
You can make an init script in the SysV manner to backup/restore the data in /var/lib/rancher instead of symlink.

Answer 16 · 2016-03-22T00:40:40.000Z

Anyway, rancher-agent should work in such a situation.

Answer 17 · 2016-03-22T00:47:08.000Z

Oh great idea ! I try 😃

Answer 18 · 2016-03-22T00:54:52.000Z

Wait a minute.
-v /var/lib/rancher:/var/lib/rancher rancher/agent:v0.9.2 means that /var/lib/rancher has already existed at run the container. ??? I don't understand that failure.

Answer 19 · 2016-03-22T00:55:57.000Z

Ok works !

But, if the VM crash, no backup 😟

Answer 20 · 2016-03-22T00:59:39.000Z

Yes, this command to add custom host :

sudo docker run -d --privileged -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/rancher:/var/lib/rancher rancher/agent:v0.10.0 https://infra.cedvan.com/v1/scripts/4A21993727DD77639CA1:1458604800000:hBFQhNHEkdXRKy8ZKtg3ItAw2gk

means that /var/lib/rancher already exist with symbolic link create before first run

Answer 21 · 2016-03-22T01:06:45.000Z

Ok great !

My solution :

lib-persistent-folder.sh

#!/bin/sh
#
# Configure lib persistent folder....
#


case "$1" in
  install)
        echo "Install lib persistent folder..."
        rm -f /var/lib/docker
        rm -f /var/lib/docker-root
        cp -rf /var/lib/* /mnt/sda1/var/lib/
        rm -rf /var/lib
        ln -s /mnt/sda1/var/lib /var/lib
        ;;
  start)
    echo "Mount lib persistent folder..."
        rm -rf /var/lib
    ln -s /mnt/sda1/var/lib /var/lib
    ;;
  stop)
    printf "Unmount lib persitent folder..."
    rm -f /var/lib
    ;;
  restart|reload)
    "$0" stop
    "$0" start
    ;;
  *)
    echo "Usage: $0 {install|start|stop|restart}"
    exit 1
esac

exit $?

Vagrantfile

...

order = 60
script_name_source = "lib-persistent-folder.sh"
script_name_destination = "S#{order}lib-persistent-folder"
node.vm.provision "file", source: "./#{script_name_source}", destination: "/tmp/#{script_name_destination}"
node.vm.provision "shell",
inline: "mv /tmp/#{script_name_destination} /etc/init.d/#{script_name_destination} && chmod +x /etc/init.d/#{script_name_destination} && /etc/init.d/#{script_name_destination} install"

...

Answer 22 · 2016-03-22T01:09:34.000Z

With this solution data saved on crash :)

Answer 23 · 2016-03-22T01:13:49.000Z

Why do you not make persistent the folder /var completely ?

Answer 24 · 2016-03-22T01:16:26.000Z

It is not a good idea to remove /var/lib/docker on provision while running Docker daemon.

I just follow the boot2docker way about /var/lib/docker.

Answer 25 · 2016-03-22T01:22:51.000Z

Ok, it is better to stop docker daemon, delete, create the symbolic link /var/lib and restart the docker daemon ?

  install)
        echo "Install lib persistent folder..."
        /etc/init.d/docker stop
        rm -f /var/lib/docker
        rm -f /var/lib/docker-root
        cp -rf /var/lib/* /mnt/sda1/var/lib/
        rm -rf /var/lib
        ln -s /mnt/sda1/var/lib /var/lib
        /etc/init.d/docker start
        ;;

Answer 26 · 2016-03-22T01:33:23.000Z

Those script should be in start for every boot.
DockerRoot /init will create symlinks to /var/lib/docker and /var/lib/docker-root again on boot.

BTW,
Why don't you open an issue for this at rancher/agent repo?

Answer 27 · 2016-03-22T01:38:35.000Z

In start, you don't need to stop/start Docker daemon, because Docker daemon stops in the init.d process.

Answer 28 · 2016-03-22T01:39:20.000Z

Issue to rancher/rancher is open rancher/rancher#4073 😉

Answer 29 · 2016-03-22T01:41:42.000Z

Step install is executed on provisioning, so docker daemon is running. Stop/start docker is necessary no ?
Steps start and stop executed by init.d, so not need stop/start docker

Answer 30 · 2016-03-22T01:48:10.000Z

Step install is executed on provisioning, so docker daemon is running.
Stop/start docker is necessary.

Yes

Steps start and stop executed by init.d, so not need stop/start docker

No, you don't need.

Answer 31 · 2016-03-22T01:49:10.000Z

Ok, so my solution is good ?
(Just to wait that rancher/rancher solve problem)

Answer 32 · 2016-03-22T02:00:23.000Z

Let me see the final version of your script. Probably fine.

Answer 33 · 2016-03-22T02:02:29.000Z

lib-persistent-folder.sh

#!/bin/sh
#
# Configure lib persistent folder....
#

case "$1" in
  install)
        echo "Install lib persistent folder..."
        /etc/init.d/docker stop
        rm -f /var/lib/docker
        rm -f /var/lib/docker-root
        cp -rf /var/lib/* /mnt/sda1/var/lib/
        rm -rf /var/lib
        ln -s /mnt/sda1/var/lib /var/lib
        /etc/init.d/docker start
        ;;
  start)
    echo "Mount lib persistent folder..."
        rm -rf /var/lib
    ln -s /mnt/sda1/var/lib /var/lib
    ;;
  stop)
    printf "Unmount lib persitent folder..."
    rm -f /var/lib
    ;;
  restart|reload)
    "$0" stop
    "$0" start
    ;;
  *)
    echo "Usage: $0 {install|start|stop|restart}"
    exit 1
esac

exit $?

Vagrantfile

...

order = 60
script_name_source = "lib-persistent-folder.sh"
script_name_destination = "S#{order}lib-persistent-folder"
node.vm.provision "file", source: "./#{script_name_source}", destination: "/tmp/#{script_name_destination}"
node.vm.provision "shell",
    inline: "mv /tmp/#{script_name_destination} /etc/init.d/#{script_name_destination} && chmod +x /etc/init.d/#{script_name_destination} && /etc/init.d/#{script_name_destination} install"

...

Answer 34 · 2016-03-22T02:12:11.000Z

I guess,

        rm -f /var/lib/docker
        rm -f /var/lib/docker-root
        cp -rf /var/lib/* /mnt/sda1/var/lib/
        rm -rf /var/lib
        ln -s /mnt/sda1/var/lib /var/lib

should be in start for every boot.

Answer 35 · 2016-03-22T02:12:43.000Z

Did you try -v /mnt/sda1/var/lib/rancher:/var/lib/rancher ?

Answer 36 · 2016-03-22T02:15:15.000Z

should be in start for every boot.

Why ?

Did you try -v /mnt/sda1/var/lib/rancher:/var/lib/rancher ?

Lol, no I don't try, I wanted to keep rancher default config. But I'll try 😄

Answer 37 · 2016-03-22T02:17:34.000Z

Works 😝 !

Answer 38 · 2016-03-22T02:19:07.000Z

should be in start for every boot.
Why ?

DockerRoot /init script creates symlinks /var/lib/docker and /var/lib/docker-root before init.d scripts on every boot.

Answer 39 · 2016-03-22T02:21:21.000Z

Ok, I understand

Answer 40 · 2016-03-22T05:44:52.000Z

Why do you not make persistent the folder /var completely ?

Other system processes like syslog and programs use under /var, so it's not good to move completely even on boot.