linuxserver/planka pulls statistics

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. • Discussions - 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/planka

Planka is an elegant open source project tracking tool.

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/planka: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

Web UI is accessible at http://SERVERIP:PORT. An external postgres database is required.

Once you've run your first time setup you can safely remove the DEFAULT_ environment variables. They will overwrite any changes made to the default user in the web UI (passwords, display names, etc.) on startup if left in place.

Migration from Official Image

Copy your user-avatars, background-images, and attachments folders to your new /config mount so that it looks like:

Read-Only Operation

This image can be run with a read-only container filesystem. For details please read the docs.

Non-Root Operation

This image can be run with a non-root user. For details please read the docs.

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)

docker cli (click here for more info)

Parameters

Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate : 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 |

| -p 1337:1337 | Planka web UI. | | -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 BASE_URL=https://planka.example.com | The URL you will use to access planka including protocol, and port if not 80/443. | | -e DATABASE_URL=postgresql://user:password@planka-db:5432/planka | Postgres database URL. Special characters must be url encoded. | | -e DEFAULT_ADMIN_EMAIL=demo@demo.demo | Email address for default user. | | -e DEFAULT_ADMIN_USERNAME=demo | Username for default user. | | -e DEFAULT_ADMIN_PASSWORD=demo | Password for default user. | | -e DEFAULT_ADMIN_NAME=Demo User | Display name for default user. | | -e SECRET_KEY=notasecretkey | Session encryption key, recommended 32-64 character alphanumeric. | | -e TRUST_PROXY=false | Set to true to trust upstream proxies if reverse proxying. | | -e DEFAULT_LANGUAGE=en-US | This sets the default language for sending notifications per user (if a user hasn't selected a language) and per board. | | -v /config | Local path for planka config files. | | --read-only=true | Run container with a read-only filesystem. Please read the docs. | | --user=1000:1000 | Run container with a non-root user. Please read the docs. |

Environment variables from files (Docker secrets)

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

As an example:

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:

Example output:

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: • To monitor the logs of the container in realtime: • Container version number: • Image version number:

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: • Single image: • Update containers: • All containers: • Single container: • You can also remove the old dangling images:…

Description from the Docker Hub listing.