Skip to main content

Use JuiceFS in Docker

The simplest way would be using bind mount, you can directly mount JuiceFS into container using -v, assuming the host mount point being /jfs:

docker run -d --name nginx \
-v /jfs/html:/usr/share/nginx/html \
-p 8080:80 \

If you wish to control mount points using Docker, so that different application containers may use different JuiceFS file systems, you can use our Docker volume plugin.

Docker volume plugin

Every Docker plugin itself is a Docker image, and JuiceFS Docker volume plugin is packed with JuiceFS Community Edition as well as JuiceFS Cloud Service clients, after installation, you'll be able to run this plugin, and create JuiceFS Volume inside Docker.

Install the plugin with the following command, grant permissions when asked:

docker plugin install juicedata/juicefs

You can manage volume plugin with the following commands:

# Disable the volume plugin
docker plugin disable juicedata/juicefs

# Upgrade plugin (need to disable first)
docker plugin upgrade juicedata/juicefs
docker plugin enable juicedata/juicefs

# Uninstall plugin
docker plugin rm juicedata/juicefs

Create volume

Create a new volume using the following command, if you forget how to obtain relevant credentials, revisit Creating a file system:

docker volume create -d juicedata/juicefs \
-o name=$VOL_NAME -o token=$JFS_TOKEN \
-o accesskey=$ACCESS_KEY -o secretkey=$SECRET_KEY jfsvolume

If you need to pass extra environment variables to the auth/mount process (e.g. Google Cloud Platform), append them as -o env=FOO=bar,SPAM=egg.

Usage and management

# Mount the volume in container
docker run -it -v jfsvolume:/opt busybox ls /opt

# After a volume has been unmounted, delete using the following command
# Deleting a volume only remove the relevant resources from Docker, which doesn't affect data stored in JuiceFS
docker volume rm jfsvolume

Using Docker Compose

Example for creating and mounting JuiceFS volume with docker-compose:

version: '3'
image: busybox
command: "ls /jfs"
- jfsvolume:/jfs
driver: juicedata/juicefs
name: ${VOL_NAME}
token: ${JFS_TOKEN}
access-key: ${ACCESS_KEY}
secret-key: ${SECRET_KEY}
# Pass extra environment variables using env
# env: FOO=bar,SPAM=egg

Common management commands:

# Start the service
docker-compose up

# Shut down the service and remove Docker volumes
docker-compose down --volumes

Use in Docker Swarm

JuiceFS volume can be shared in Docker Swarm. Make sure that volume plugin juicedata/juicefs is installed on every worker node.

Pass options to --mount to create service mounting JuiceFS volume.

docker service create --name nginx --mount \
type=volume,volume-driver=juicedata/juicefs,source=jfsvolume,destination=/jfs, \
volume-opt=name=$VOL_NAME,volume-opt=token=$JFS_TOKEN,volume-opt=accesskey=$ACCESS_KEY,volume-opt=secretkey=$SECRET_KEY nginx:alpine


If JuiceFS Docker volume plugin is not working properly, it's recommend to upgrade the volume plugin first, and then check logs to debug.

  • Collect JuiceFS Client logs, which is inside the Docker volume plugin container itself:

    # locate the docker plugins runtime directory, your environment may differ from below example
    # container directories will be printed, directory name is container ID
    ls /run/docker/plugins/runtime-root/plugins.moby

    # print plugin container info
    # if container list is empty, that means plugin container didn't start properly
    # read the next step to continue debugging
    runc --root /run/docker/plugins/runtime-root/plugins.moby list

    # collect log inside plugin container
    runc --root /run/docker/plugins/runtime-root/plugins.moby exec 452d2c0cf3fd45e73a93a2f2b00d03ed28dd2bc0c58669cca9d4039e8866f99f cat /var/log/juicefs.log

    If it is found that the container doesn't exist (ls found that the directory is empty), or that juicefs.log doesn't exist, this usually indicates a bad mount, check plugin logs to further debug.

  • Collect plugin log, for example under systemd:

    journalctl -f -u docker | grep "plugin="

    juicefs is called to perform the actual mount inside the plugin container, if any error occurs, it will be shown in the Docker daemon logs, same when there's error with the volume plugin itself.