clecherbauer/docker-volume-bindfs

Docker volume plugin for bindfs

docker-volume-bindfs's Issues

No longer able to use this plugin without sudo

Hello,

I used this plugin quite a long time but unfortunately I don't get it to run on an updated machine. I use Ubuntu on a normal desktop PC. Nothing special here.

I followed these steps to install docker:

• https://docs.docker.com/engine/install/ubuntu/
• https://docs.docker.com/engine/install/linux-postinstall/

It doesn't matter if I try to install this plugin before or after the post-installation process

Distro/Version:
Ubuntu 21.10

Installation gives:

$ docker plugin install lebokus/bindfs

Plugin "lebokus/bindfs" is requesting the following privileges:
 - mount: [/var/lib/docker/plugins/]
 - mount: [/]
 - device: [/dev/fuse]
 - capabilities: [CAP_SYS_ADMIN]
Do you grant the above permissions? [y/N] y
latest: Pulling from lebokus/bindfs
Digest: sha256:70e32e400cf4fe1c58cee67e651067d949d724fd2c7d0e9e77a44e5650c0d289
dcac74e2a670: Complete 
Error response from daemon: dial unix /run/docker/plugins/92f03adaea02541d5b87f37afa298de9d59317f73db35935a8fc0ab6b7276c6e/bindfs.sock: connect: no such file or directory

In /run/docker/plugins there is another hash belonging to root when I install the plugin with sudo.

sudo docker-compose up -d is giving:

Cannot create container for service php: VolumeDriver.Mount: exit status 1%!(EXTRA []interface {}=[])

docker-compose.yml:

version: "3.7"
services:
  nginx:
    [...]
    volumes:
      - docker-share:/var/www/html/
      [...]
    working_dir: /var/www/html/

docker-compose.override.yml:

version: "3.7"
volumes:
  docker-share:
    driver: lebokus/bindfs
    driver_opts:
      sourcePath: "${pwd}/www/html"
      map: "${UID:-1000}/33:@${UID:-1000}/@33"

What did I miss?

Very verbose "error" messages that don't seem to be errors

@lebokus Firstly, thanks for this plugin. :)

In the docker logs (using docker in docker), I see logs of examples of

time="2021-08-24T17:18:47Z" level=error msg="2021/08/24 17:18:47 Entering go-plugins-helpers getPath" plugin=61cd6bca634b9df27c29b4c824873d3afa87ab0dedb49b8149cfd3570579ff6c
time="2021-08-24T17:18:47Z" level=error msg="2021/08/24 17:18:47 Entering go-plugins-helpers capabilitiesPath" plugin=61cd6bca634b9df27c29b4c824873d3afa87ab0dedb49b8149cfd3570579ff6c
time="2021-08-24T17:18:47Z" level=error msg="2021/08/24 17:18:47 Entering go-plugins-helpers capabilitiesPath" plugin=61cd6bca634b9df27c29b4c824873d3afa87ab0dedb49b8149cfd3570579ff6c
time="2021-08-24T17:18:47Z" level=error msg="2021/08/24 17:18:47 Entering go-plugins-helpers getPath" plugin=61cd6bca634b9df27c29b4c824873d3afa87ab0dedb49b8149cfd3570579ff6c
time="2021-08-24T17:18:47Z" level=error msg="2021/08/24 17:18:47 Entering go-plugins-helpers capabilitiesPath" plugin=61cd6bca634b9df27c29b4c824873d3afa87ab0dedb49b8149cfd3570579ff6c

These don't seem to cause any negative effects and I've not set the DEBUG flag.

Is it possible to silence these messages?

VolumeDriver.Mount: exit status 1

When I run:

docker volume create --driver lebokus/bindfs:latest -o sourcePath=$PWD -o map=$UID/1000:@$UID/@1000 some_volume > /dev/null
docker run -v some_volume:/home/ ubuntu:20.04     

I experience:

docker: Error response from daemon: VolumeDriver.Mount: exit status 1%!(EXTRA []interface {}=[]).

This may be connected with this issue and this issue

(Reproduced on Mac OS Catalina 10.15.7, Docker version 20.10.10, latest version of bindfs plugin)

CRITICAL: when mounting the same directory twice the source directory get's deleted

When I the same container with the same source directory using this plugin twice, the source directory on the host is removed.

There is forked version of this plugin (https://github.com/StudioEtrange/docker-volume-bindfs.) which doesn't seem to have this problem.

The error message looks the same as reported in #4.

Clarify options

Cool plugin!

Reading through the code, it looks like the driver_opts (other than sourcePath) translate directly to the options passed into bindfs (1). Would be good to document that in the readme.

provide a build pipeline