where does the docker plugin install fetches from ?
How can I modify it for my needs ? I suppose there's a github or dockerhub repo, how can I fork it, and how do I tell docker plugin install to use my forked plugin ?
Still looking where is the source code.
From docker plugin install rclone/docker-volume-rclone I would assume that it is a reference to a github repo.
But https://github.com/orgs/rclone/docker-volume-rclone does not seem to exist or be accessible.
Is this a private repo ? What did I miss ?
Yes thank you. But that's not what I'm asking.
If I want to do and test some hacks on that plugin, where do I start in practice ?
I need to be able to install my modified plugin, right ?
@kforner
So you want make derivative kforner/docker-volume-rclone on docker hub.
First off, everything in rclone/docker-plugin-rclone is built from and by the main rclone repo.
I do have mine ivandeex/docker-volume-rclone on docker hub based on rclone master with a few patches that I need now, still waiting for ncw attention for some months.
The commit below has all you needed to derive a.t.m.:
Use the line PLUGIN_IMAGE_USER=kforner, reverse-engineer down to Makefile/Dockerfile and voila.
Managed plugin is in fact a special container running in a namespace separate from normal docker containers. Inside it runs the rclone serve docker command.
The config and cache directories are bind-mounted into the container at start. The docker daemon connects to a unix socket created by the command inside the container. The command creates on-demand remote mounts right inside, then docker machinery propagates them through kernel mount namespaces and bind-mounts into requesting user containers.