Pydio-cells

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.

Image details

Pulls: 246k

Architectures: amd64, arm64

Image size: 146 MB

Latest: 5.0.2

User: linuxserver

Created: Dec 14, 2019

Updated: 2 days ago

Status: active

Configuration

Type

Container

Platform

linux

Image

linuxserver/pydio-cells:latest

Ports

8080:8080/tcp

Volumes

/config : /srv/lsio/pydio-cells/config

Env vars

PUID=1000PGID=1000TZ=Etc/UTCEXTERNALURL=yourdomain.urlSERVER_IP=0.0.0.0

Restart

unless-stopped

Template by technorabilia

Notes

Portainer App Templates by Technorabilia, based on data provided by LinuxServer.io.

Ensure to create the following volume directories on the host file system, or modify the paths in the volume mapping section under the advanced options below, as needed.

mkdir -p /srv/lsio/pydio-cells/config

Installation

Ensure both Docker and Portainer are installed, and up-to-date
Log into your Portainer web UI
Under Settings → App Templates, paste the below URL
Head to Home → App Templates, and the list of apps will show up
Select the app you wish to deploy, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json

Show Me

docker run -d --name Pydio-cells \
  -p 8080:8080/tcp \
  -e 'PUID=1000' \
  -e 'PGID=1000' \
  -e 'TZ=Etc/UTC' \
  -e 'EXTERNALURL=yourdomain.url' \
  -e 'SERVER_IP=0.0.0.0' \
  -v /srv/lsio/pydio-cells/config:/config \
  --restart=unless-stopped \
  linuxserver/pydio-cells:latest

Save this file as compose.yaml and run docker compose up -d
Use this only as a guide.

services:
  pydio-cells:
    image: linuxserver/pydio-cells:latest
    ports:
      - 8080:8080/tcp
    volumes:
      - /srv/lsio/pydio-cells/config:/config
    environment:
      PUID: '1000'
      PGID: '1000'
      TZ: Etc/UTC
      EXTERNALURL: yourdomain.url
      SERVER_IP: 0.0.0.0
    restart: unless-stopped

Save this file as pydio-cells-stack.yml, then from a manager node, run docker stack deploy -c pydio-cells-stack.yml pydio-cells

version: '3.8'
services:
  pydio-cells:
    image: linuxserver/pydio-cells:latest
    ports:
      - 8080:8080/tcp
    volumes:
      - /srv/lsio/pydio-cells/config:/config
    environment:
      PUID: '1000'
      PGID: '1000'
      TZ: Etc/UTC
      EXTERNALURL: yourdomain.url
      SERVER_IP: 0.0.0.0
    deploy:
      restart_policy:
        condition: any

Save each file below into a folder, then run kubectl apply -f .
Written for k3s, but works on any cluster: bind mounts use hostPath, named volumes get a persistent volume claim, and ports are exposed via a LoadBalancer service.

`pydio-cells-deployment.yaml`

apiVersion: apps/v1
kind: Deployment
metadata:
  name: pydio-cells
  labels:
    app: pydio-cells
spec:
  replicas: 1
  selector:
    matchLabels:
      app: pydio-cells
  template:
    metadata:
      labels:
        app: pydio-cells
    spec:
      containers:
        - name: pydio-cells
          image: linuxserver/pydio-cells:latest
          env:
            - name: PUID
              value: '1000'
            - name: PGID
              value: '1000'
            - name: TZ
              value: Etc/UTC
            - name: EXTERNALURL
              value: yourdomain.url
            - name: SERVER_IP
              value: 0.0.0.0
          ports:
            - containerPort: 8080
              protocol: TCP
          volumeMounts:
            - name: pydio-cells-data-0
              mountPath: /config
      volumes:
        - name: pydio-cells-data-0
          hostPath:
            path: /srv/lsio/pydio-cells/config

`pydio-cells-service.yaml`

apiVersion: v1
kind: Service
metadata:
  name: pydio-cells
spec:
  type: LoadBalancer
  selector:
    app: pydio-cells
  ports:
    - name: 8080-tcp
      port: 8080
      targetPort: 8080
      protocol: TCP

Save this file as ~/.config/containers/systemd/pydio-cells.container

[Unit]
Description=Pydio-cells

[Container]
Image=linuxserver/pydio-cells:latest
ContainerName=pydio-cells
PublishPort=8080:8080/tcp
Environment=PUID=1000
Environment=PGID=1000
Environment=TZ=Etc/UTC
Environment=EXTERNALURL=yourdomain.url
Environment=SERVER_IP=0.0.0.0
Volume=/srv/lsio/pydio-cells/config:/config

[Service]
Restart=always

[Install]
WantedBy=default.target

Then reload systemd and start the service:

systemctl --user daemon-reload
systemctl --user start pydio-cells

For a system-wide service, use /etc/containers/systemd/ and drop --user.

For more installation options, see the Documentation in our GitHub repo

The LinuxServer.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

linuxserver/pydio-cells

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.

Supported Architectures

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.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:
| Architecture | Available | Tag | | :----: | :----: | ---- | | x86-64 | ✅ | amd64-\ | | arm64 | ✅ | arm64v8-\ |

Application Setup

You must first create a mysql database for Pydio Cells. Using our mariadb image is recommended.
Then access the web gui setup wizard at https://SERVER_IP:8080 if accessing locally (must set SERVER_IP env var), or at https://pydio-cells.domain.com if reverse proxying.

Strict reverse proxies

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

Usage

To help you get started creating a container from this image you can either use docker-compose or the docker cli.
>!NOTE >Unless a parameter is flagged as 'optional', it is mandatory and a value must be provided.

docker-compose (recommended, click here for more info)

---
services:
  pydio-cells:
    image: lscr.io/linuxserver/pydio-cells:latest
    container_name: pydio-cells
    hostname: pydio-cells
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - EXTERNALURL=yourdomain.url
      - SERVER_IP=0.0.0.0 #optional
    volumes:
      - /path/to/pydio-cells/config:/config
    ports:
      - 8080:8080
    restart: unless-stopped

docker cli (click here for more info)

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

Parameters

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 port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.
| Parameter | Function | | :----: | --- | | --hostname= | Pydio Cells uses the hostname to verify local files. This setting is required and should not be changed after it has been set. | | -p 8080:8080 | Http port | | -e PUID=1000 | for UserID - see below for explanation | | -e PGID=1000 | for GroupID - see below for explanation | | -e TZ=Etc/UTC | specify a timezone to use, see this list. | | -e EXTERNALURL=yourdomain.url | The external url you would like to use to access Pydio Cells (Can be https://domain.url or https://IP:PORT). | | -e SERVER_IP=0.0.0.0 | Enter the LAN IP of the docker server. Required for local access by IP, added to self signed cert as SAN (not required if accessing only through reverse proxy). | | -v /config | All the config files reside here. |

Environment variables from files (Docker secrets)

You can set any environment variable from a file by using a special prepend FILE__.
As an example:

-e FILE__MYVAR=/run/secrets/mysecretvariable

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

Umask for running applications

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 up here before asking for support.

User / Group Identifiers

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 user PUID and group PGID.
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 instance PUID=1000 and PGID=1000, to find yours use id your_user as below:

id your_user

Example output:

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

Docker Mods

We publish various Docker 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.

Support Info

Shell access whilst the container is running:

```bash
docker exec -it pydio-cells /bin/bash
```

To monitor the logs of the container in realtime:

```bash
docker logs -f pydio-cells
```

Container version number:

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

Image version number:

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

Updating Info

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 the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:

Via Docker Compose

Update images:

* All images:

    ```bash
    docker-compose pull
    ```

* Single image:

    ```bash
    docker-compose pull pydio-cells
    ```

Update containers:

* All containers:

    ```bash
    docker-compose up -d
    ```

* Single container:

    ```bash
    docker-compose up -d pydio-cells
    ```

You can also remove the old dangling images:

```bash
docker image prune
```

Via Docker Run

Update the image:

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

Stop the running container:

```bash
docker stop pydio-cells
```

Delete the container:

```bash
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:

```bash
docker image prune
```

Image Update Notifications - Diun (Docker Image Update Notifier)

>!TIP >We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.

Building locally

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.git
cd docker-pydio-cells
docker build \
  --no-cache \
  --pull \
  -t lscr.io/linuxserver/pydio-cells:latest .

The ARM variants can be built on x8664 hardware and vice versa using lscr.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.
Versions
17.07.26: - Rebasing to Alpine 3.24.
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 announced here
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, add SERVER_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

Serve Pydio-cells on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxy Domain App port Upstream

Proxying pydio-cells.example.com to http://Pydio-cells:8080

Add this to your Caddyfile

pydio-cells.example.com {
	reverse_proxy http://Pydio-cells:8080
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

In Portainer, go to Containers, click the container, then Logs. Or run docker logs Pydio-cells
Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:8080 failed: port is already allocated", something else on your server is using that port.

Find what's using it: sudo ss -tlnp | grep :8080
Stop the other service, or pick a different host port. In 8080:8080 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

Use your server's real IP: http://your-server-ip:8080. The 0.0.0.0 link Portainer shows isn't a real address.
Give it a minute after first deploy, Pydio-cells can take a while to initialise.
Make sure your firewall allows the port, e.g. sudo ufw allow 8080

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

Fix the ownership: sudo chown -R 1000:1000 /srv/lsio/pydio-cells/config
Or set the PUID and PGID variables (defaults 1000:1000) to match your own user, found with id $USER

Image won't pull

Test the pull directly on the host: docker pull linuxserver/pydio-cells:latest

"manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
"toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
"no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

This image supports: amd64, arm64
Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

Check the logs right after a restart, the last few lines before it died are the useful ones.
Get the exit code with docker inspect Pydio-cells --format '{{.State.ExitCode}}'
Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

Bug within the app: Open an issue within Pydio-cells's repo
Template not working: Open an issue on technorabilia/portainer-templates
This website not working: Open an issue on lissy93/portainer-templates

Similar apps

PairDrop File Sharing

Projectsend File Sharing

Pwndrop File Sharing

Xbackbone File Sharing