I installed gitlab-ce from original package repository of gitlab-ce. It's installed successfully.
root#gitlab-ce:~# gitlab-ctl status
run: alertmanager: (pid 48831) 429s; run: log: (pid 38226) 5557s
run: gitaly: (pid 48833) 429s; run: log: (pid 38220) 5557s
run: gitlab-exporter: (pid 48835) 429s; run: log: (pid 38218) 5557s
run: gitlab-kas: (pid 48844) 429s; run: log: (pid 38219) 5557s
run: gitlab-workhorse: (pid 48847) 429s; run: log: (pid 38215) 5557s
run: logrotate: (pid 48850) 429s; run: log: (pid 38232) 5557s
run: nginx: (pid 49783) 1s; run: log: (pid 38222) 5557s
run: node-exporter: (pid 48861) 429s; run: log: (pid 38228) 5557s
run: postgres-exporter: (pid 48871) 429s; run: log: (pid 38234) 5557s
run: postgresql: (pid 48873) 429s; run: log: (pid 38216) 5557s
run: prometheus: (pid 48877) 429s; run: log: (pid 38230) 5557s
run: puma: (pid 48883) 429s; run: log: (pid 38217) 5557s
run: redis: (pid 48886) 429s; run: log: (pid 38221) 5557s
run: redis-exporter: (pid 48890) 429s; run: log: (pid 38224) 5557s
run: sidekiq: (pid 48893) 429s; run: log: (pid 38223) 5557s
Its IP address is 192.168.0.110, When I use http://192.168.0.110 in my browser, It open default web page of Debian, Not gitlab pages.
How can I access to gitlab pages?
Related
after re-installing docker sudo snap install docker on
francesco#francesco-yoga720:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal
francesco#francesco-yoga720:~$ docker --version
Docker version 19.03.13, build cd8016b6bc
francesco#francesco-yoga720:~$ sudo docker pull docker/whalesay
Using default tag: latest
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
[edit]
docker info
Client:
Context: default
Debug Mode: false
Plugins:
app: Docker App (Docker Inc., v0.9.1-beta3)
buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info
/etc/docker/daemon.json
francesco#francesco-yoga720:~$ cat /etc/docker/daemon.json
cat: /etc/docker/daemon.json: No such file or directory
as the error seems quite common I try to follow the (many) answers offered here
but nothing worked
systemctl start docker (etc)
francesco#francesco-yoga720:~$ sudo systemctl start docker
francesco#francesco-yoga720:~$ sudo systemctl enable docker
Synchronizing state of docker.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable docker
francesco#francesco-yoga720:~$ sudo systemctl restart docker
francesco#francesco-yoga720:~$ sudo systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2021-02-21 11:20:43 EET; 1min 53s ago
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Main PID: 902441 (dockerd)
Tasks: 13
Memory: 42.1M
CGroup: /system.slice/docker.service
└─902441 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
veebr 21 11:20:42 francesco-yoga720 dockerd[902441]: time="2021-02-21T11:20:42.743739283+02:00" level=warning msg="Your kernel does not support CPU realtime scheduler"
veebr 21 11:20:42 francesco-yoga720 dockerd[902441]: time="2021-02-21T11:20:42.743768279+02:00" level=warning msg="Your kernel does not support cgroup blkio weight"
veebr 21 11:20:42 francesco-yoga720 dockerd[902441]: time="2021-02-21T11:20:42.743782740+02:00" level=warning msg="Your kernel does not support cgroup blkio weight_device"
veebr 21 11:20:42 francesco-yoga720 dockerd[902441]: time="2021-02-21T11:20:42.743999793+02:00" level=info msg="Loading containers: start."
veebr 21 11:20:42 francesco-yoga720 dockerd[902441]: time="2021-02-21T11:20:42.946560909+02:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip c>
veebr 21 11:20:43 francesco-yoga720 dockerd[902441]: time="2021-02-21T11:20:43.031108724+02:00" level=info msg="Loading containers: done."
veebr 21 11:20:43 francesco-yoga720 dockerd[902441]: time="2021-02-21T11:20:43.074547710+02:00" level=info msg="Docker daemon" commit=46229ca graphdriver(s)=zfs version=20.10.3
veebr 21 11:20:43 francesco-yoga720 dockerd[902441]: time="2021-02-21T11:20:43.074672376+02:00" level=info msg="Daemon has completed initialization"
veebr 21 11:20:43 francesco-yoga720 systemd[1]: Started Docker Application Container Engine.
veebr 21 11:20:43 francesco-yoga720 dockerd[902441]: time="2021-02-21T11:20:43.122623201+02:00" level=info msg="API listen on /run/docker.sock"
francesco#francesco-yoga720:~$
francesco#francesco-yoga720:~$ sudo docker pull docker/whalesay
Using default tag: latest
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
service docker restart
francesco#francesco-yoga720:~$ sudo service docker restart
francesco#francesco-yoga720:~$ sudo docker pull docker/whalesay
Using default tag: latest
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
sudo snap start docker
francesco#francesco-yoga720:~$ sudo snap start docker
Started.
francesco#francesco-yoga720:~$
francesco#francesco-yoga720:~$ sudo docker pull docker/whalesay
Using default tag: latest
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
service docker start
francesco#francesco-yoga720:~$ sudo service docker start
francesco#francesco-yoga720:~$ sudo docker pull docker/whalesay
Using default tag: latest
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
sudo dockerd
francesco#francesco-yoga720:~$ sudo dockerd
INFO[2021-02-21T11:26:46.777903160+02:00] Starting up
failed to start daemon: pid file found, ensure docker is not running or delete /var/run/docker.pid
sudo nohup docker daemon (etc)
francesco#francesco-yoga720:~$ sudo nohup docker daemon -H tcp://0.0.0.0:2375 -H unix:///var/run/docker.sock
nohup: ignoring input and appending output to 'nohup.out'
francesco#francesco-yoga720:~$ sudo usermod -aG docker $USER
francesco#francesco-yoga720:~$ sudo docker pull docker/whalesay
Using default tag: latest
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
EDIT with new attempts:
sudo rm -rf /var/run/docker.pid
francesco#francesco-yoga720:~$ sudo rm -rf /var/run/docker.pid
francesco#francesco-yoga720:~$ sudo docker pull docker/whalesay
Using default tag: latest
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
francesco#francesco-yoga720:~$ sudo snap start docker
Started.
francesco#francesco-yoga720:~$ sudo docker pull docker/whalesay
Using default tag: latest
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
providing sudo snap logs docker
francesco#francesco-yoga720:~$ sudo snap logs docker
2021-02-21T11:00:35Z systemd[1]: Started Service for snap application docker.dockerd.
2021-02-21T11:00:36Z docker.dockerd[16902]: time="2021-02-21T13:00:36.204337202+02:00" level=error msg="failed to mount overlay: invalid argument" storage-driver=overlay2
2021-02-21T11:00:37Z docker.dockerd[16902]: failed to start daemon: error initializing graphdriver: driver not supported
2021-02-21T11:00:37Z systemd[1]: snap.docker.dockerd.service: Main process exited, code=exited, status=1/FAILURE
2021-02-21T11:00:37Z systemd[1]: snap.docker.dockerd.service: Failed with result 'exit-code'.
2021-02-21T11:00:37Z systemd[1]: snap.docker.dockerd.service: Scheduled restart job, restart counter is at 5.
2021-02-21T11:00:37Z systemd[1]: Stopped Service for snap application docker.dockerd.
2021-02-21T11:00:37Z systemd[1]: snap.docker.dockerd.service: Start request repeated too quickly.
2021-02-21T11:00:37Z systemd[1]: snap.docker.dockerd.service: Failed with result 'exit-code'.
2021-02-21T11:00:37Z systemd[1]: Failed to start Service for snap application docker.dockerd.
I don't know what else to try, any suggestion?
I have tried too many times,but I failed.
I run order in shell ,it works,but I write it to supervisor or /etc/rc.d/init.d/functions ,both failed!
/usr/sbin/rabbitmq-server start (shell works)
supervisor or /etc/rc.d/init.d/functions ,both failed!
RabbitMQ on Centos7 uses the systemd.
You have to enable the service:
sudo systemctl enable rabbitmq-server
Then try to reboot:
Last login: Tue Sep 5 07:51:49 2017 from 10.0.2.2
[vagrant#localhost ~]$ sudo systemctl status rabbitmq-server
● rabbitmq-server.service - RabbitMQ broker
Loaded: loaded (/usr/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2017-09-05 07:57:05 UTC; 20s ago
Main PID: 930 (beam.smp)
Status: "Initialized"
CGroup: /system.slice/rabbitmq-server.service
├─ 930 /usr/lib64/erlang/erts-9.0.4/bin/beam.smp -W w -A 64 -P 1048576 -t 5000000 -stbt db -zdbbl 128000 -K true -- -root /usr/lib64/erlang -progname erl -- -home /var/lib/rabbitmq -- -pa /usr/lib/rabbitmq/lib/rabbitmq_server-3.6.11.902/ebin -noshell -n...
├─1317 /usr/lib64/erlang/erts-9.0.4/bin/epmd -daemon
├─2354 erl_child_setup 1024
├─2437 inet_gethost 4
└─2438 inet_gethost 4
EDIT
It is the same for 3.3.5, see here:
[vagrant#localhost ~]$ sudo systemctl status rabbitmq-server
● rabbitmq-server.service - LSB: Enable AMQP service provided by RabbitMQ broker
Loaded: loaded (/etc/rc.d/init.d/rabbitmq-server; bad; vendor preset: disabled)
Active: inactive (dead)
Docs: man:systemd-sysv-generator(8)
[vagrant#localhost ~]$ sudo systemctl enable rabbitmq-server
rabbitmq-server.service is not a native service, redirecting to /sbin/chkconfig.
Executing /sbin/chkconfig rabbitmq-server on
[vagrant#localhost ~]$ sudo reboot
➜ centos7 vagrant ssh
Last login: Tue Sep 5 08:04:37 2017 from 10.0.2.2
[vagrant#localhost ~]$ sudo systemctl status rabbitmq-server
● rabbitmq-server.service - LSB: Enable AMQP service provided by RabbitMQ broker
Loaded: loaded (/etc/rc.d/init.d/rabbitmq-server; bad; vendor preset: disabled)
Active: active (running) since Tue 2017-09-05 08:48:23 UTC; 9s ago
Docs: man:systemd-sysv-generator(8)
Process: 972 ExecStart=/etc/rc.d/init.d/rabbitmq-server start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/rabbitmq-server.service
├─1325 /bin/sh /etc/rc.d/init.d/rabbitmq-server start
├─1335 /bin/bash -c ulimit -S -c 0 >/dev/null 2>&1 ; /usr/sbin/rabbitmq-server
└─1339 /bin/sh /usr/sbin/rabbitmq-server
RabbitMQ version:
sudo rabbitmqctl status
Status of node rabbit#localhost ...
[{pid,1379},
{running_applications,[{rabbit,"RabbitMQ","3.3.5"},
Note:
You are using a very old RabbitMQ version, please consider to update it to the last one
I start pm2on booting my raspberry pi 3 with ONE of theses shell scripts (rc.local executed as root during boot)
As root user
code
startPm2Root() {
#delete to avoid all pm2 issues
rm -rf "$PM2_HOME"
pkill -f pm2
USER="root"
HOME="/root"
PM2_HOME="$HOME/.pm2"
export USER HOME PM2_HOME
pm2 startup systemd &
if [ -f /home/pi/app/newVersion.tar.gz ]; then
bash /home/pi/app/deploy.sh
else
pm2 kill && pm2 start /home/pi/app/processes.json &
fi
pm2 save
}
problem/log
+ USER=root
+ HOME=/root
+ PM2_HOME=/root/.pm2
+ export USER HOME PM2_HOME
+ [ -f /home/pi/app/newVersion.tar.gz ]
+ pm2 startup systemd
+ pm2 save
+ pm2 kill
[PM2] Spawning PM2 daemon with pm2_home=/root/.pm2
[PM2] Spawning PM2 daemon with pm2_home=/root/.pm2
[PM2] Init System found: systemd
Platform systemd
Template
[Unit]
Description=PM2 process manager
Documentation=https://pm2.keymetrics.io/
After=network.target
[Service]
Type=forking
User=root
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
Environment=PATH=/usr/bin:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
Environment=PM2_HOME=/root/.pm2
PIDFile=/root/.pm2/pm2.pid
ExecStart=/usr/lib/node_modules/pm2/bin/pm2 resurrect
ExecReload=/usr/lib/node_modules/pm2/bin/pm2 reload all
ExecStop=/usr/lib/node_modules/pm2/bin/pm2 kill
[Install]
WantedBy=multi-user.target
Target path
/etc/systemd/system/pm2-root.service
Command list
[ 'chmod +x /etc/systemd/system/pm2-root.service',
'systemctl enable pm2-root',
'systemctl start pm2-root',
'systemctl daemon-reload',
'systemctl status pm2-root' ]
[PM2] Writing init configuration in /etc/systemd/system/pm2-root.service
[PM2] Making script booting at startup...
>>> Executing chmod +x /etc/systemd/system/pm2-root.service
[DONE]
>>> Executing systemctl enable pm2-root
[DONE]
>>> Executing systemctl start pm2-root
[PM2] PM2 Successfully daemonized
[PM2] Stopping PM2...
[PM2][WARN] No process found
[PM2] All processes have been stopped and deleted
[PM2] PM2 stopped
+ pm2 start /home/pi/app/processes.json
[PM2] Spawning PM2 daemon with pm2_home=/root/.pm2
[DONE]
>>> Executing systemctl daemon-reload
[DONE]
>>> Executing systemctl status pm2-root
● pm2-root.service - PM2 process manager
Loaded: loaded (/etc/systemd/system/pm2-root.service; enabled)
Active: active (running) since Fri 2017-06-30 16:36:29 UTC; 199ms ago
Docs: https://pm2.keymetrics.io/
Main PID: 1034 (PM2 v2.5.0: God)
CGroup: /system.slice/pm2-root.service
└─1034 PM2 v2.5.0: God Daemon (/root/.pm2)
Jun 30 16:36:27 grassberry pm2[1021]: [PM2] Spawning PM2 daemon with pm2_home=/root/.pm2
Jun 30 16:36:29 grassberry pm2[1021]: [PM2] PM2 Successfully daemonized
Jun 30 16:36:29 grassberry pm2[1021]: [PM2] Resurrecting
Jun 30 16:36:29 grassberry pm2[1021]: [PM2] Restoring processes located in /root/.pm2/dump.pm2
Jun 30 16:36:29 grassberry pm2[1021]: [PM2][ERROR] No processes saved; DUMP file doesn't exist
Jun 30 16:36:29 grassberry pm2[1021]: ┌──────────┬────┬──────┬─────┬────────┬─────────┬────────┬─────┬─────┬──────────┐
Jun 30 16:36:29 grassberry pm2[1021]: │ App name │ id │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ watching │
Jun 30 16:36:29 grassberry pm2[1021]: └──────────┴────┴──────┴─────┴────────┴─────────┴────────┴─────┴─────┴──────────┘
Jun 30 16:36:29 grassberry pm2[1021]: Use `pm2 show <id|name>` to get more details about an app
Jun 30 16:36:29 grassberry systemd[1]: Started PM2 process manager.
[DONE]
+---------------------------------------+
[PM2] Freeze a process list on reboot via:
$ pm2 save
[PM2] Remove init script via:
$ pm2 unstartup systemd
As pi
code
startPm2Pi() {
#delete to avoid all pm2 issues
rm -rf "$PM2_HOME"
pkill -f pm2
USER="pi"
HOME="/home/pi"
PM2_HOME="$HOME/.pm2"
export USER HOME PM2_HOME
pm2 startup systemd -u pi & #also tried it without -u
if [ -f /home/pi/app/newVersion.tar.gz ]; then
bash /home/pi/app/deploy.sh
else
pm2 kill && pm2 -u pi start /home/pi/app/processes.json &
fi
pm2 save
}
problem
Error: connect EACCES /home/pi/.pm2/rpc.sock
Also it looks like I got multiple processes running:
root#gb:/home/pi# ps -aux | grep pm2
root 946 1.8 3.4 87908 32172 ? Sl 16:36 0:01 node /usr/bin/pm2 start /home/pi/app/processes.json
root 947 2.1 3.3 87872 31500 ? Sl 16:36 0:01 node /usr/bin/pm2 save
root 990 1.6 2.9 81372 28096 ? Ssl 16:36 0:01 PM2 v2.5.0: God Daemon (/root/.pm2)
root 1034 1.5 3.0 81892 28396 ? Ssl 16:36 0:01 PM2 v2.5.0: God Daemon (/root/.pm2)
root 1040 1.5 2.9 81136 28160 ? Ssl 16:36 0:01 PM2 v2.5.0: God Daemon (/root/.pm2)
pi 1090 7.5 2.9 81520 28216 ? Ssl 16:37 0:01 PM2 v2.5.0: God Daemon (/home/pi/.pm2)
Looks stable so far, I removed the startup script, I think it is either the one (startup) or the other (start).
Removed all fragments from startup for pi
sudo env PATH=$PATH:/usr/bin /usr/lib/node_modules/pm2/bin/pm2 unstartup systemd -u pi --hp /home/pi
and root
sudo pm2 unstartup
And stripped the code to:
startPm2Root() {
#delete to avoid all pm2 issues
rm -rf "$PM2_HOME"
pkill -f pm2
USER="root"
HOME="/root"
PM2_HOME="$HOME/.pm2"
export USER HOME PM2_HOME
#pm2 startup systemd & <= removed this
pm2 kill && pm2 start /home/pi/app/processes.json &
#pm2 save <= removed this, launches a second instance somehow
}
How can I restart mongodb that I just killed in Linux?
Before killing:
$ service mongodb status
● mongodb.service - An object/document-oriented database
Loaded: loaded (/lib/systemd/system/mongodb.service; disabled; vendor preset: enabled)
Active: active (running) since Tue 2017-01-03 08:41:16 GMT; 4h 5min ago
Docs: man:mongod(1)
Main PID: 1036 (mongod)
Tasks: 10
Memory: 61.0M
CPU: 1min 1.636s
CGroup: /system.slice/mongodb.service
└─1036 /usr/bin/mongod --config /etc/mongodb.conf
So I wanted to stop/ kill it for a while for other programs:
$ sudo kill 1036
$ service mongodb status
● mongodb.service - An object/document-oriented database
Loaded: loaded (/lib/systemd/system/mongodb.service; disabled; vendor preset: enabled)
Active: inactive (dead)
Docs: man:mongod(1)
But how can I start it again?
I'm on Ubuntu 16.04.
EDIT:
$ systemctl start mongod
Failed to start mongod.service: Unit mongod.service not found.
EDIT 2:
Get this error below when I have the other program running on mondodb. so I killed that program and it works as before.
$ sudo systemctl start mongodb
$ service mongodb status
● mongodb.service - An object/document-oriented database
Loaded: loaded (/lib/systemd/system/mongodb.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2017-01-03 13:05:19 GMT; 9s ago
Docs: man:mongod(1)
Process: 21732 ExecStart=/usr/bin/mongod --config /etc/mongodb.conf (code=exited, status=48)
Main PID: 21732 (code=exited, status=48)
Ubuntu 16.04 LTS
sudo systemctl start mongodb
Not only for MongoDB, but for any application installed, you can use
sudo systemctl start <app_name>
sudo systemctl restart <app_name>
Seems like you are using systemd
Try:
systemctl start mongod -> Start the service
systemctl status mongod -> Status of service
systemctl restart mongod -> restart the service
systemctl reload mongod -> reload the service
You checked status with :
service mongod status
so this should start mongod:
service mongod start
so this should stop mongod:
sudo service mongod stop
It works at my end.
for missing permissions:
sudo service mongod start
Got the following error while using flocker, can any body help? I'm using CentOS7.
[root#agentNode ~]# docker run -v apples:/data --volume-driver flocker busybox sh -c "echo hello > /data/file.txt"
docker: Error response from daemon: create apples: create apples: Error looking up volume plugin flocker: plugin not found.
See '/usr/bin/docker-current run --help'.
[root#testnode7 ~]# docker run -ti -v volumename:/data --volume-driver=flocker busybox sh
docker: Error response from daemon: create volumename: create volumename: Error looking up volume plugin flocker: plugin not found.
See '/usr/bin/docker-current run --help'.
kindly run docker -v and share the result, i suspect something changed in latest docker release 1.12, also share your flocker service logs
cat /var/log/flocker/flocker-docker-plugin.log
I think I have the same problem here.
[root#manager1 vagrant]# docker version
Client:
Version: 1.12.2
API version: 1.24
Go version: go1.6.3
Git commit: bb80604
Built:
OS/Arch: linux/amd64
Server:
Version: 1.12.2
API version: 1.24
Go version: go1.6.3
Git commit: bb80604
Built:
OS/Arch: linux/amd64
check if clusterhq-flocker-docker-plugin installed
[root#manager1 vagrant]# yum install clusterhq-flocker-docker-plugin
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.ventraip.net.au
* epel: mirror.overthewire.com.au
* extras: centos.mirror.serversaustralia.com.au
* updates: centos.mirror.serversaustralia.com.au
Package clusterhq-flocker-docker-plugin-1.15.0-1.noarch already installed and latest version
Nothing to do
ok check status flocker-dataset-agent
[root#manager1 vagrant]# systemctl status flocker-dataset-agent
● flocker-dataset-agent.service - Flocker Dataset Agent
Loaded: loaded (/usr/lib/systemd/system/flocker-dataset-agent.service; disabled; vendor preset: disabled)
Active: active (running) since Fri 2016-10-14 02:57:41 BST; 1s ago
Main PID: 16908 (flocker-dataset)
Memory: 33.7M
CGroup: /system.slice/flocker-dataset-agent.service
└─16908 /opt/flocker/bin/python /usr/sbin/flocker-dataset-agent --journald
Oct 14 02:57:41 manager1 systemd[1]: flocker-dataset-agent.service holdoff time over, scheduling restart.
Oct 14 02:57:41 manager1 systemd[1]: Started Flocker Dataset Agent.
Oct 14 02:57:41 manager1 systemd[1]: Starting Flocker Dataset Agent...
ok check status flocker-container-agent
[root#manager1 vagrant]# systemctl status flocker-container-agent
● flocker-container-agent.service - Flocker Container Agent
Loaded: loaded (/usr/lib/systemd/system/flocker-container-agent.service; disabled; vendor preset: disabled)
Active: active (running) since Fri 2016-10-14 02:57:56 BST; 760ms ago
Main PID: 17032 (flocker-contain)
Memory: 23.2M
CGroup: /system.slice/flocker-container-agent.service
└─17032 /opt/flocker/bin/python /usr/sbin/flocker-container-agent --journald
Oct 14 02:57:56 manager1 systemd[1]: Started Flocker Container Agent.
Oct 14 02:57:56 manager1 systemd[1]: Starting Flocker Container Agent...
check status flocker-docker-plugin
[root#manager1 vagrant]# systemctl status flocker-docker-plugin
● flocker-docker-plugin.service - Flocker Docker Plugin
Loaded: loaded (/usr/lib/systemd/system/flocker-docker-plugin.service; disabled; vendor preset: disabled)
Active: inactive (dead)
enable and restart
[root#manager1 vagrant]# systemctl enable flocker-docker-plugin
Created symlink from /etc/systemd/system/multi-user.target.wants/flocker-docker-plugin.service to /usr/lib/systemd/system/flocker-docker-plugin.service.
[root#manager1 vagrant]# systemctl restart flocker-docker-plugin
[root#manager1 vagrant]# systemctl status flocker-docker-plugin
● flocker-docker-plugin.service - Flocker Docker Plugin
Loaded: loaded (/usr/lib/systemd/system/flocker-docker-plugin.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2016-10-14 02:59:40 BST; 1s ago
Main PID: 17973 (flocker-docker-)
Memory: 43.9M
CGroup: /system.slice/flocker-docker-plugin.service
└─17973 /opt/flocker/bin/python /usr/sbin/flocker-docker-plugin --journald
Oct 14 02:59:40 manager1 systemd[1]: flocker-docker-plugin.service holdoff time over, scheduling restart.
Oct 14 02:59:40 manager1 systemd[1]: Started Flocker Docker Plugin.
Oct 14 02:59:40 manager1 systemd[1]: Starting Flocker Docker Plugin...
OK try again
[root#manager1 vagrant]# docker volume create --name persistent-vol-11 -d flocker
Error response from daemon: create persistent-vol-11: create persistent-vol-11: Error looking up volume plugin flocker: plugin not found
try using the plugin with docker run
[root#manager1 vagrant]# docker run -v apples:/data --volume-driver flocker busybox sh -c "echo hello > /data/file.txt"
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
56bec22e3559: Pull complete
Digest: sha256:29f5d56d12684887bdfa50dcd29fc31eea4aaf4ad3bec43daf19026a7ce69912
Status: Downloaded newer image for busybox:latest
docker: Error response from daemon: create apples: create apples: Error looking up volume plugin flocker: plugin not found.