search

MatchbookLab / local-persist

Create named local volumes that persist in the location(s) you want
MIT License
852 stars 123 forks source link

docker plugin ls #47

Closed smebberson closed 7 years ago

smebberson commented 7 years ago

When this plugin is installed correctly, should running docker plugin ls produce anything related to this plugin?

smebberson commented 7 years ago

I'm pretty sure it didn't install correctly, because I restarted the database container (after everything was all working), and my app no longer functioned due to missing data.

Is there anyway to diagnose the install?

I received the following message after installation:

sudo curl -fsSL https://raw.githubusercontent.com/CWSpear/local-persist/master/scripts/install.sh | sudo bash -s --       
Stopping docker-volume-local-persist service if running

Downloading binary:
  From: https://github.com/CWSpear/local-persist/releases/download/v1.3.0/local-persist-linux-amd64
  To:   /usr/bin/docker-volume-local-persist
Binary download

Downloading Systemd service conf:
  From: https://raw.githubusercontent.com/CWSpear/local-persist/v1.3.0/init/systemd.service
  To:   /etc/systemd/system/docker-volume-local-persist.service
Systemd conf downloaded

Starting docker-volume-local-persist service...
* docker-volume-local-persist.service - docker-volume-local-persist
   Loaded: loaded (/etc/systemd/system/docker-volume-local-persist.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2017-02-23 15:44:33 ACDT; 29ms ago
 Main PID: 8992 (docker-volume-l)
    Tasks: 3
   Memory: 2.4M
      CPU: 5ms
   CGroup: /system.slice/docker-volume-local-persist.service
           `-8992 /usr/bin/docker-volume-local-persist

Feb 23 15:44:33 idearium-common systemd[1]: Started docker-volume-local-persist.
Feb 23 15:44:33 idearium-common docker-volume-local-persist[8992]: Starting...       Found 1 volumes on startup

Done! If you see this message, that should mean everything is installed and is running.

I have a feeling no output relating to this plugin from the command docker plugin ls doesn't really matter. Prior to installing it, I ran a docker-compose up and it complained about a plugin that it didn't know about. After installing it, my containers started fine...

However, the volumes are definitely not being persisted.

System info:

Containers: 3
 Running: 3
 Paused: 0
 Stopped: 0
Images: 18
Server Version: 1.13.0
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 49
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins: 
 Volume: local local-persist
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 03e5862ec0d8d3b3f750e19fca3ee367e13c090e
runc version: 2f7393a47307a16f8cee44a37b262e8b81021e3e
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.4.0-63-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 992.3 MiB
Name: idearium-common
ID: DR6J:BFOC:NLXG:Z64M:Z22G:73BH:C2NZ:6XQN:5YVT:PX4B:PQXE:IIA2
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

(I just noticed it mentions this plugin in the output above...)

Any ideas?

smebberson commented 7 years ago

Do you know what? I'm an idiot. I had incorrectly mapped my volume, and there had two volumes to the container. The data was being written the standard Docker local plugin, not this one - which works perfectly :)

CWSpear commented 7 years ago

Glad you figured it out :-)