简体   繁体   English

找不到flocker插件,来自守护程序的错误响应

[英]flocker plugin not found, error response from daemon

Got the following error while using flocker , can any body help? 使用flocker出现以下错误,请问有什么身体帮助的吗? I'm using CentOS7 . 我正在使用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'.

请运行docker -v并共享结果,我怀疑在最新的docker版本1.12中有所更改,还共享了您的flocker服务日志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 检查是否安装了clusterhq-flocker-docker-plugin

[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 确定检查状态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 ok检查状态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 检查状态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 尝试将插件与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.

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 docker:来自守护程序的错误响应:找不到网络 mysql_net - docker: Error response from daemon: network mysql_net not found docker:来自守护进程的错误响应:无效模式:/usr/src/app - docker: Error response from daemon: invalid mode: /usr/src/app 为什么我的 NVIDIA docker 不工作? 来自守护进程的错误响应? - why is my NVIDIA docker not working? Error response from daemon? Docker 来自守护进程的错误响应:“冲突......容器已在使用” - Docker error response from daemon: "Conflict ... already in use by container" Docker 来自守护程序的错误响应:无法安装本地卷 - Docker Error response from daemon: failed to mount local volume 如何解决“docker:来自守护进程的错误响应:OCI 运行时创建失败:无法检索 OCI 运行时错误” - How to solve "docker: Error response from daemon: OCI runtime create failed: unable to retrieve OCI runtime error" 来自守护进程的错误响应:加入会话密钥环:创建会话密钥:超出磁盘配额 - Error response from daemon: join session keyring: create session key: disk quota exceeded 当我尝试使用docker pull peterevans / nominatim时来自守护进程的错误响应 - Error response from daemon when i'm trying docker pull peterevans/nominatim “来自守护进程的错误响应:无法启动容器......没有这样的文件或目录”在Oracle Linux上运行hello-world - “Error response from daemon: Cannot start container … no such file or directory” on Oracle Linux running hello-world 来自守护进程的错误响应:获取 https://registry-1.docker.io/v2/:远程错误:tls:握手失败 - Error response from daemon: Get https://registry-1.docker.io/v2/: remote error: tls: handshake failure
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM