Repository files navigation

TheLinuxServer.io team brings you another container release featuring:

• regular and timely application updates
• easy user mappings (PGID, PUID)
• custom base image with s6 overlay
• weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
• regular security updates

Find us at:

• Blog - all the things you can do with our containers including How-To guides, opinions and much more!
• Discord - realtime support / chat with the community and the team.
• Discourse - post on our community forum.
• GitHub - view the source for all of our repositories.
• Open Collective - please consider helping us by either donating or contributing to our budget

Pydio-cells is the nextgen file sharing platform for organizations. It is a full rewrite of the Pydio project using the Go language following a micro-service architecture.

We utilise the docker manifest for multi-platform awareness. More information is available from dockerhere and our announcementhere.

Simply pullinglscr.io/linuxserver/pydio-cells:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

You must first create a mysql database for Pydio Cells. Using ourmariadb image is recommended.

Then access the web gui setup wizard athttps://SERVER_IP:8080 if accessing locally (must setSERVER_IP env var), or athttps://pydio-cells.domain.com if reverse proxying.

This image uses a self-signed certificate by default. This naturally means the scheme ishttps.If you are using a reverse proxy which validates certificates, you need todisable this check for the container.

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

---services:pydio-cells:image:lscr.io/linuxserver/pydio-cells:latestcontainer_name:pydio-cellshostname:pydio-cellsenvironment:      -PUID=1000      -PGID=1000      -TZ=Etc/UTC      -EXTERNALURL=yourdomain.url      -SERVER_IP=0.0.0.0#optionalvolumes:      -/path/to/pydio-cells/config:/configports:      -8080:8080restart:unless-stopped

docker run -d \  --name=pydio-cells \  --hostname=pydio-cells \  -e PUID=1000 \  -e PGID=1000 \  -e TZ=Etc/UTC \  -e EXTERNALURL=yourdomain.url \  -e SERVER_IP=0.0.0.0`#optional` \  -p 8080:8080 \  -v /path/to/pydio-cells/config:/config \  --restart unless-stopped \  lscr.io/linuxserver/pydio-cells:latest

Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate<external>:<internal> respectively. For example,-p 8080:80 would expose port80 from inside the container to be accessible from the host's IP on port8080 outside the container.

You can set any environment variable from a file by using a special prependFILE__.

As an example:

-e FILE__MYVAR=/run/secrets/mysecretvariable

Will set the environment variableMYVAR based on the contents of the/run/secrets/mysecretvariable file.

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional-e UMASK=022 setting.Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read uphere before asking for support.

When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the userPUID and groupPGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instancePUID=1000 andPGID=1000, to find yours useid your_user as below:

id your_user

Example output:

uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)

We publish variousDocker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.

• Shell access whilst the container is running:

  dockerexec -it pydio-cells /bin/bash

• To monitor the logs of the container in realtime:

  docker logs -f pydio-cells

• Container version number:

  docker inspect -f'{{ index .Config.Labels "build_version" }}' pydio-cells

• Image version number:

  docker inspect -f'{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/pydio-cells:latest

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult theApplication Setup section above to see if it is recommended for the image.

Below are the instructions for updating containers:

• Update images:

  • All images:

    docker-compose pull

  • Single image:

    docker-compose pull pydio-cells

• Update containers:

  • All containers:

    docker-compose up -d

  • Single container:

    docker-compose up -d pydio-cells

• You can also remove the old dangling images:

  docker image prune

• Update the image:

  docker pull lscr.io/linuxserver/pydio-cells:latest

• Stop the running container:

  docker stop pydio-cells

• Delete the container:

  docker rm pydio-cells

• Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your/config folder and settings will be preserved)

• You can also remove the old dangling images:

  docker image prune

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone https://github.com/linuxserver/docker-pydio-cells.gitcd docker-pydio-cellsdocker build \  --no-cache \  --pull \  -t lscr.io/linuxserver/pydio-cells:latest.

The ARM variants can be built on x86_64 hardware and vice versa usinglscr.io/linuxserver/qemu-static

docker run --rm --privileged lscr.io/linuxserver/qemu-static --reset

Once registered you can define the dockerfile to use with-f Dockerfile.aarch64.

• 27.07.25: - Rebasing to Alpine 3.22.
• 27.06.24: - Rebasing to Alpine 3.20.
• 14.03.24: - Rebasing to alpine 3.19. Grpc port defaults to 8080.
• 11.10.23: - Rebasing to alpine 3.18. Build on alpine edge with Go 1.21.
• 06.07.23: - Deprecate armhf. As announcedhere
• 01.12.22: - Rebasing to alpine 3.17. Adding multi-arch support. Updating cli arguments for v4 compatibility.
• 19.10.22: - Rebasing to alpine 3.16. Upgrading to s6v3. Updating build instructions for v4.
• 19.09.22: - Rebasing to alpine 3.15.
• 23.01.21: - Rebasing to alpine 3.13.
• 01.06.20: - Rebasing to alpine 3.12.
• 18.04.20: - Switch to https as default (only affects new installs). Add self signed cert, addSERVER_IP var for adding to cert as SAN. Add optional gRPC port mapping for CellsSync.
• 17.04.20: - Update compile options, previous release was broken for new installs.
• 19.12.19: - Rebasing to alpine 3.11.
• 12.12.19: - Initial Release