moby: cloudstor.sock: connect: no such file or directory
Description Trying to install the azure cloudstor plugin on a docker installation on-premise (not on Docker for Azure). The only documentation I could find seems to concern Docker for Azure. Is this plugin even compatible for on-premise setups?
Error response from daemon: dial unix /run/docker/plugins/b3d498c8c4714dfc271f72e32656e81224f8c00151f404f459db512e4ac62bb0/cloudstor.sock: connect: no such file or directory
Steps to reproduce the issue:
sudo docker swarm init
sudo docker plugin install --alias cloudstor:azure \
--grant-all-permissions docker4x/cloudstor:18.09.2-ce-azure1 \
CLOUD_PLATFORM=AZURE \
AZURE_STORAGE_ACCOUNT_KEY="$AZURE_STORAGE_ACCOUNT_KEY" \
AZURE_STORAGE_ACCOUNT="$AZURE_STORAGE_ACCOUNT" \
DEBUG=1
Describe the results you received:
Error response from daemon: dial unix /run/docker/plugins/641a1b5d1ff1ff38ce54d7b1f785d357f37c8ec2f4f0a6f15ec221cdfb399c10/cloudstor.sock: connect: no such file or directory
ID NAME DESCRIPTION ENABLED
b3d498c8c471 cloudstor:azure cloud storage plugin for Docker false
Describe the results you expected:
ID NAME DESCRIPTION ENABLED
b3d498c8c471 cloudstor:azure cloud storage plugin for Docker true
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version
:
Client: Docker Engine - Community
Version: 18.09.2
API version: 1.39
Go version: go1.10.8
Git commit: 6247962
Built: Sun Feb 10 04:12:39 2019
OS/Arch: darwin/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 18.09.2
API version: 1.39 (minimum version 1.12)
Go version: go1.10.6
Git commit: 6247962
Built: Sun Feb 10 04:13:06 2019
OS/Arch: linux/amd64
Experimental: false
Output of docker info
:
Containers: 22
Running: 0
Paused: 0
Stopped: 22
Images: 17
Server Version: 18.09.2
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: active
NodeID: 66etpkyj3g3sr0tj60xyaz8dc
Is Manager: true
ClusterID: o9oejgvora8oyp5cnx6ol2i2l
Managers: 1
Nodes: 1
Default Address Pool: 10.0.0.0/8
SubnetSize: 24
Orchestration:
Task History Retention Limit: 5
Raft:
Snapshot Interval: 10000
Number of Old Snapshots to Retain: 0
Heartbeat Tick: 1
Election Tick: 10
Dispatcher:
Heartbeat Period: 5 seconds
CA Configuration:
Expiry Duration: 3 months
Force Rotate: 0
Autolock Managers: false
Root Rotation In Progress: false
Node Address: 192.168.65.3
Manager Addresses:
192.168.65.3:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9754871865f7fe2f4e74d43e2fc7ccd237edcbce
runc version: 09c8266bf2fcf9519a651b04ae54c967b9ab86ec
init version: fec3683
Security Options:
seccomp
Profile: default
Kernel Version: 4.9.125-linuxkit
Operating System: Docker for Mac
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 1.952GiB
Name: linuxkit-025000000001
ID: SSTC:7UCL:LONP:JPNF:C5HC:EWYG:ADSY:LAT7:JXLG:ZYK4:T5FG:UZ6N
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
File Descriptors: 38
Goroutines: 163
System Time: 2019-03-08T15:13:18.331799928Z
EventsListeners: 2
HTTP Proxy: gateway.docker.internal:3128
HTTPS Proxy: gateway.docker.internal:3129
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Product License: Community Engine
Additional environment details (AWS, VirtualBox, physical, etc.): This was tested on a mac and linux laptops and on our dev swarm server running on Red Hat Enterprise Linux Server release 7.3 on VMWare.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 1
- Comments: 16 (4 by maintainers)
FYI, I worked around this by mounting the azure file share to the docker host using SMB. Then bind mounting the host directory to the containers. In swarm mode you just need to ensure all the hosts in the swarm have the file share mapped to the same path. A working plugin would make this easier for sure.