run Ente rootless and distroless
7.0K

run Ente rootless and distroless
Enteβ (created by ente-ioβ ) is a service that provides a fully open source, end-to-end encrypted platform for you to store your data in the cloud without needing to trust the service provider. On top of this platform, we have built three apps so far: Ente Photos (an alternative to Apple and Google Photos), Ente Locker (a safe space for your most important documents and credentials), and Ente Auth (a 2FA alternative to the deprecated Authy).

What can I do with this? This image will run Ente rootlessβ and distrolessβ , for maximum security and performance. For all info's about the config file please read the documentationβ . Works with Photos, Auth and Locker.
Why should I run this image and not the other image(s) that already exist? Good question! Because ...
If you value security, simplicity and optimizations to the extreme, then this image might be for you.
Below you find a comparison between this image and the most used or original one.
| image | size on disk | init default as | distrolessβ | supported architectures |
|---|---|---|---|---|
| 11notes/ente | 32MB | 1000:1000 | β | amd64, arm64 |
| ente-io/server | 57MB | 0:0 | β | amd64, arm64 |
db:
host: "${POSTGRES_HOST}"
port: "${POSTGRES_PORT}"
name: "${POSTGRES_DATABASE}"
user: "${POSTGRES_USER}"
password: "${POSTGRES_PASSWORD}"
sslmode: disable
s3:
are_local_buckets: true
minio:
key: "admin"
secret: "${MINIO_ROOT_PASSWORD}"
endpoint: "minio:9000"
bucket: "${MINIO_BUCKET}"
log-file: ""
http:
apps:
public-albums:
cast:
accounts:
family:
key:
encryption: "yvmG/RnzKrbCb9L3mgsmoxXr9H7i2Z4qlbT0mL3ln4w="
hash: "KXYiG07wC7GIgvCSdg+WmyWdXDAn6XKYJtp/wkEU7x573+byBRAYtpTP0wwvi8i/4l37uicX1dVTUzwH3sLZyw=="
jwt:
secret: "i2DecQmfGreG6q1vBj5tCokhlN41gcfS2cjOs9Po-u8="
smtp:
host:
port:
username:
password:
email:
transmail:
key:
apple:
shared-secret:
stripe:
us:
key:
webhook-secret:
in:
key:
webhook-secret:
whitelisted-redirect-urls: []
path:
success: "?status=success&session_id={CHECKOUT_SESSION_ID}"
cancel: "?status=fail&reason=canceled"
webauthn:
rpid: localhost
rporigins:
- "http://localhost:3001"
discord:
bot:
cha-ching:
token:
channel:
mona-lisa:
token:
channel:
zoho:
client-id:
client-secret:
refresh-token:
list-key:
topic-ids:
listmonk:
server-url:
username:
password:
list-ids:
internal:
silent: false
health-check-url:
admins: []
admin:
disable-registration: false
hardcoded-ott:
local-domain-suffix:
local-domain-value:
replication:
enabled: false
worker-url:
worker-count: 6
tmp-storage: tmp/replication
jobs:
cron:
skip: false
remove-unreported-objects:
worker-count: 1
clear-orphan-objects:
enabled: false
prefix: ""
name: "ente"
x-lockdown: &lockdown
# prevents write access to the image itself
read_only: true
# prevents any process within the container to gain more privileges
security_opt:
- "no-new-privileges=true"
services:
server:
depends_on:
postgres:
condition: "service_healthy"
restart: true
minio:
condition: "service_healthy"
restart: true
mc:
condition: service_completed_successfully
image: "11notes/ente:2026.03.23"
<<: *lockdown
environment:
TZ: "Europe/Zurich"
POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}"
MINIO_ROOT_PASSWORD: "${MINIO_ROOT_PASSWORD}"
volumes:
- "server.etc:/ente/etc"
ports:
- "3000:8080/tcp"
networks:
frontend:
backend:
restart: "always"
postgres:
# for more information about this image checkout:
# https://github.com/11notes/docker-postgres
image: "11notes/postgres:18"
<<: *lockdown
environment:
TZ: "Europe/Zurich"
POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}"
networks:
backend:
volumes:
- "postgres.etc:/postgres/etc"
- "postgres.var:/postgres/var"
- "postgres.backup:/postgres/backup"
tmpfs:
- "/postgres/run:uid=1000,gid=1000"
- "/postgres/log:uid=1000,gid=1000"
restart: "always"
minio:
# for more information about this image checkout:
# https://github.com/11notes/docker-minio
image: "11notes/minio:2025.10.15"
hostname: "minio"
<<: *lockdown
environment:
TZ: "Europe/Zurich"
MINIO_ROOT_PASSWORD: "${MINIO_ROOT_PASSWORD}"
command: "/mnt"
ports:
- "3000:9001/tcp"
- "9000:9000/tcp"
volumes:
- "minio.var:/mnt"
networks:
backend:
restart: "always"
mc:
# for more information about this image checkout:
# https://github.com/11notes/docker-mc
depends_on:
minio:
condition: "service_healthy"
restart: true
image: "11notes/mc:2025.08.13"
<<: *lockdown
environment:
TZ: "Europe/Zurich"
MC_MINIO_URL: "https://minio:9000"
MC_MINIO_ROOT_PASSWORD: "${MINIO_ROOT_PASSWORD}"
MC_INSECURE: true
command:
- mb --ignore-existing minio/ente
volumes:
- "mc.etc:/mc/etc"
networks:
backend:
restart: "no"
volumes:
server.etc:
postgres.etc:
postgres.var:
postgres.backup:
minio.var:
mc.etc:
networks:
frontend:
backend:
internal: true
To find out how you can change the default UID/GID of this container image, consult the RTFMβ .
| Parameter | Value | Description |
|---|---|---|
user | docker | user name |
uid | 1000 | user identifierβ |
gid | 1000 | group identifierβ |
home | /ente | home directory of user docker |
| Parameter | Value | Default |
|---|---|---|
TZ | Time Zoneβ | |
DEBUG | Will activate debug option for container image and app (if available) | |
ENTE_CONFIG (optional) | Will overwrite the default config with the value of this variable if set (inline configβ ) |
These are the main tags for the image. There is also a tag for each commit and its shorthand sha256 value.
It is my opinion that the :latest tag is a bad habbit and should not be used at all. Many developers introduce breaking changes in new releases. This would messed up everything for people who use :latest. If you donβt want to change the tag to the latest semverβ , simply use the short versions of semverβ . Instead of using :2026.03.23 you can use :2026 or :2026.03. Since on each new version these tags are updated to the latest version of the software, using them is identical to using :latest but at least fixed to a major or minor version. Which in theory should not introduce breaking changes.
If you still insist on having the bleeding edge release of this app, simply use the :rolling tag, but be warned! You will get the latest version of the app instantly, regardless of breaking changes or security issues or what so ever. You do this at your own risk!
docker pull 11notes/ente:2026.03.23
docker pull ghcr.io/11notes/ente:2026.03.23
docker pull quay.io/11notes/ente:2026.03.23
This image supports unraid by default. Simply add -unraid to any tag and the image will run as 99:100 instead of 1000:1000.
This image supports nobody by default. Simply add -nobody to any tag and the image will run as 65534:65534 instead of 1000:1000.
This image is not based on another image but uses scratchβ as the starting layer. The image consists of the following distroless layers that were added:
This image is provided to you at your own risk. Always make backups before updating an image to a different version. Check the releasesβ for breaking changes. If you have any problems with using this image simply raise an issueβ , thanks. If you have a question or inputs please create a new discussionβ instead of an issue. You can find all my other repositories on githubβ .
created 05.05.2026, 00:24:54 (CET)
Content type
Image
Digest
sha256:b731856c2β¦
Size
30.2 MB
Last updated
5 months ago
docker pull 11notes/ente:2026.03.23-nobody