r/docker • • 5h ago

whats your trick for keeping docker image sizes small without breaking stuff

3 Upvotes

i keep seeing images that are over a gig for simple apps. multi stage builds help but sometimes slim or alpine base images break things. curious how people handle this in practice.


r/docker • • 9h ago

How do you move forward time in the Docker stack

Thumbnail
reddit.com
0 Upvotes

r/docker • • 13h ago

Docker Error Help

Thumbnail reddit.com
1 Upvotes

r/docker • • 17h ago

how to make migrations service just run once in docker stack per deploy

0 Upvotes

EDIT: this is the thing that i had to add

   deploy:
      restart_policy:
        condition: on-failure
        delay: 5s
        max_attempts: 3
        window: 120s

in a production setting what would be the way to make the migrations service just run once when a deployment is made

currently my service gets restarted each time even if the migrations were succesful, which is not what i want (or expected) i just want the migration to run once per deployment with the docker stack

or if you have another whole workflow for this im very open to read it :D

migrations:
    environment:
      DB_HOST: db
      DB_NAME_FILE: /run/secrets/db-name
      DB_PASSWORD_FILE: /run/secrets/db-password
      DB_PORT: "5432"
      DB_USER_FILE: /run/secrets/db-user
      GOOSE_DRIVER: postgres
      GOOSE_MIGRATION_DIR: /migrations
    image: mymigrationimage:latest
    networks:
      db_net: null
    secrets:
      - source: db-password
        target: /run/secrets/db-password
      - source: db-user
        target: /run/secrets/db-user
      - source: db-name
        target: /run/secrets/db-name
    volumes:
      - type: bind
        source: ./init/goose-entrypoint.sh
        target: /scripts/goose-entrypoint.sh
        bind:
          create_host_path: true

this is my customish docker image for the migrations (i just made a script that sets up the credentials variables using secrets for goose)

FROM ghcr.io/kukymbr/goose-docker:3.28.0
WORKDIR /migrations

RUN apk add --no-cache bash

COPY db/migrations/* /migrations

ENTRYPOINT ["/scripts/goose-entrypoint.sh"]

r/docker • • 1d ago

I don't understand WUD

5 Upvotes

Hello everybody, I thought I got the Idea of WUD but apparently I'm not:
I have WUD configured, that he ignores all Containers in first sight:

wud docker-compose.yml

environment:
- WUD_WATCHER_LOCAL_WATCHBYDEFAULT=false

That works, no Containers show up in the Container list in the Webinterface of WUD.

Then I have a forgejo Container. I want to stay in the LTS Branch, which is actually Version Number 15 https://endoflife.date/forgejo Because I want to have the minor updates and patches I want to update my forgejo-Instance.
I thought the Idea of WUD is now, I pin the Version Number 15, WUD collects the digest of the local Container and compares it, with the actual digest of Version 15. This is what I tried:

forgejo docker-compose.yml

image: codeberg.org/forgejo/forgejo:15
labels:
- wud.watch=true
- wud.watch.digest=true
- wud.image.digest=true

The Versions of forgejo are listed here: https://codeberg.org/forgejo/-/packages/container/forgejo/versions

But WUD tells me: There is an upgrade to Version 17: (little red Batch with 17 in the "Update" Coloumn of WUD Containers Overview.

Where I'm thinking wrong? Any help is welcome!

Kindly regards!


r/docker • • 2d ago

do you pin base images by digest or just by tag

4 Upvotes

i have a few small services on compose and a couple of side projects. most of my Dockerfiles just say FROM node:20-slim or FROM python:3.12-slim and i rebuild when i feel like it. last month a rebuild pulled a newer base and a native dependency broke, so now i am wondering about pinning with sha256 digests. the downside i see is that you stop getting security patches unless something like renovate or dependabot bumps the digest for you. so for people running real stuff, do you pin by digest and have a bot update it, pin by a full version tag like 3.12.4-slim, or just use the plain tag and accept the risk? and does it change for dev vs prod images?


r/docker • • 1d ago

Move from Truenas app to native

Thumbnail reddit.com
1 Upvotes

r/docker • • 2d ago

New Icon?

23 Upvotes

Just updated to version 4.100.0 on my Mac. Did Docker just get a new icon/logo??


r/docker • • 2d ago

which sslmode in postgres to use

0 Upvotes

i have a docker stack with a postgres image, is it completly necesary to have the postgres to be configured with the ssl mode to verify-full , because, the outside world cannot interact with the db, just the backend server can (the network is not attachable and it doesn't expose any ports)

sorry if this is a little bit of a stretch because is not a full docker docker thing u.u


r/docker • • 3d ago

do you pin docker image versions or just use latest for small side stuff

38 Upvotes

pinning feels safer but then you forget to bump it and it gets old. latest is easy but a surprise update can break things. where do you land for stuff that is not production


r/docker • • 4d ago

Running Docker overlay2 on S3 Storage Using s3backer and ext4

3 Upvotes

I recently ran into a shortage of disk space on my VPS. I currently rent a VPS for €7 a month with this configuration: 4 vCPUs, 8 GB of RAM, and a 120 GB NVMe drive. It has 50 GB of free space left. But I need to run a Docker container whose image is 76 GB. I could upgrade my current VPS to get a 240 GB disk, but that would cost €30 a month. That’s steep. I noticed that my hosting provider offers 250 GB of S3 storage for just €4 a month, accessible over its internal network. So I started wondering how I could turn it into a filesystem and have Docker store files there.

First, I tried rclone. It lets you create a FUSE filesystem from your S3 storage. To speed things up, you can cache frequently used files on a local SSD using the --vfs-cache-max-size flag. Unfortunately, Docker uses overlay2, which requires filesystem operations that rclone mount does not guarantee: atomic renames, correct chmod and chown behavior, hard links, and extended attributes. In short, a full POSIX filesystem is needed.

And I found a solution: s3backer. It has 600+ stars on GitHub and provides a full-fledged ext4 filesystem. I set a 20 GB cache on my local SSD using the --blockCacheSize option, mounted it at /mnt/s3, and reconfigured Docker to store images, containers, and volumes there. As a result, the most frequently used files are cached locally instead of being pulled over the network from S3. What do you think? Expanding my virtual machine’s disk space by 250 GB for €4 a month? Pretty great, if you ask me!

By the way, here’s a summary table of the available options:

SolutionHow it worksProsCons
s3backer + ext4S3 as a block deviceFull POSIX filesystem, Docker compatibility, cachingComplex setup, latency, risk of filesystem corruption
rclone mountFUSE over S3Simple setup, local cache, support for multiple cloud providersIncomplete POSIX compatibility, some operations are unsupported
s3fsFUSE over S3Simple mounting, familiar file operationsSlow metadata operations, POSIX limitations
JuiceFSDistributed filesystem on top of S3POSIX, caching, high performanceRequires separate metadata storage
S3QLFilesystem on top of S3POSIX, compression, deduplication, encryptionExtra overhead, complex recovery

Of course, s3backer is far from the only way to turn S3 into a filesystem. There are at least two other interesting projects: JuiceFS and S3QL. Both run on top of S3, support POSIX operations and local caching, but they seemed like overkill for my use case.

JuiceFS is a fairly powerful distributed filesystem. It supports multiple servers working concurrently, caching, POSIX, and much more. But there’s a catch: in addition to S3 itself, it requires a separate metadata store. This could be Redis, PostgreSQL, MySQL, or even a local SQLite database. The last option doesn’t require a separate service, but you still have to keep the metadata database safe and back it up. Overall, it’s an interesting solution, especially if you have a server cluster. But I only have one VPS, and I didn’t want to set up extra infrastructure just to store Docker images.

S3QL is another interesting option. It supports POSIX, local caching, compression, deduplication, and encryption. It doesn’t need a separate database server: metadata is stored in SQLite and synchronized with the object store. But these extra features come at the cost of added complexity. Deduplication requires computing hashes, compression uses CPU time, and recovering the filesystem after a failure may require checking and restoring metadata with specialized tools. These aren’t critical drawbacks, but I didn’t see any particular advantages for my use case, either.

The key difference lies in the approach: JuiceFS and S3QL implement filesystems themselves using FUSE, while s3backer provides virtual block storage on top of which you can create a standard ext4 filesystem. As a result, Docker works with the familiar Linux filesystem, and s3backer translates block operations into requests to S3. No separate metadata databases, no deduplication, and no extra layers of file management.

Of course, this setup has its downsides too. Random reads and writes can be heavily affected by S3 latency, and losing the connection to the storage can bring the containers to a halt. A serious failure could also corrupt the filesystem. So I wouldn’t use this setup for critical databases. But for storing large Docker images that are downloaded once and then mostly read, it seemed perfectly reasonable-especially when S3 is available over the hosting provider’s local network. In short, I wanted an extra 250 GB for €4 a month without building a distributed storage system. From that perspective, s3backer seemed like the best fit.


r/docker • • 4d ago

Docker root question

6 Upvotes

I am a networking novice and I am using AI (claude) to guide me through installing and testing Immich on a homelab server (ubuntu 26.04) We are discussing the setup and one of the things immich needs is docker. The ai is telling me that docker needs to run its service as root (by default.) it says it can be run as a non-root user, but that requires different packages and more setup.

I just wanted to touch base with reality here since I am working with an AI. Claude has been fairly realistic about the risks, i.e. that the main risk would be if there is ever a mistake in the docker code or if something is misconfigured an attacker could gain root access, which could happen to any program running as root. I don't think the AI is being overly pessimistic, but I just wanted to see what some actual humans think ... and hopefully they won't just use an AI to respond :)

Does it make sense to try and run docker as a non-root user? what are the realistic risks here? Nothing is installed yet and there is no particular hurry, this is just a test project.

Thanks very much!


r/docker • • 5d ago

Route homelab Docker through specific interface

3 Upvotes

I created my homelab with docker running on Debian that is a VM sitting on Proxmox 9. I have two interfaces connected to the Debian server ens18 (192.168.20.21) and ens19 (192.168.20.23). I want all but 1 docker container (via docker compose) to use ens18 to receive and send traffic on. I only want ens19 to receive traffic for one port, this port is already in use in other docker containers and can't be used there so needed its own interface. I created a bridge (bridge_21) and specified com.docker.network.host_ipv4=192.168.20.21, the other bridge (bridge_23) I didn't specify any options on. I have the bridge_21 specified for the ngnix proxy manager specified below but it still seems to be routing traffic out on bridge_23's ip address. How can I get this to only route data in and out on bridge_21?

#Bridges settings
docker network create \
  --driver bridge \
  -o com.docker.network.host_ipv4=192.168.20.21 \
  bridge_21

#Ngnix Proxy Manager Compose.
services:
  app:
    container_name: ngnixproxymanager
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    networks:
      - bridge_21
    ports:
      # These ports are in format <host-port>:<container-port>
      - '192.168.20.21:80:80' # Public HTTP Port
      - '192.168.20.21:443:443' # Public HTTPS Port
      - '192.168.20.21:81:81' # Admin Web Port
    volumes:
      - type: volume
        source: ngnixproxymanager_data
        target: /data
        volume:
          subpath: data
      - type: volume
        source: ngnixproxymanager_data
        target: /etc/letsencrypt
        volume:
          subpath: letsencrypt
          
volumes:
  ngnixproxymanager_data:
    external: true

networks:
  bridge_21:
    external: true

#Weather Station docker compose
services:
  cc0ac-weather:
    build:
      context: https://github.com/akienm/CC0AC-Weather.git
      dockerfile: setup/docker/Dockerfile
    container_name: acurite-weather
    image: cc0ac-weather
    networks:
      - default
      - bridge_23
    #network_mode: bridge
    ports:
      - '192.168.20.23:443:443' # the Access hub's uploads (HTTPS)
      - '192.168.20.21:12345:12345' # dashboard and setup page
      - '192.168.20.21:12346:12346' # console uploads
    volumes:
      - acurite_data:/data
volumes:
  acurite_data:
    external: true
networks:
  bridge_23:
    external: true

r/docker • • 5d ago

Mod Approved I built a self-hosted UI for Docker Compose across multiple hosts (single binary, no paid tier) - Dockmesh

0 Upvotes

Hi r/docker,

I've been running Docker Compose on a few machines at home for years. Over that time I've tried quite a few management UIs, but never really found one that worked the way I wanted.

Some didn't quite fit my workflow, others had things like SSO, multiple hosts or backups locked behind a paid tier. Eventually I decided to build my own.

It's called Dockmesh, and I've just released version 0.5.1.

A bit about how it works

Dockmesh is a web UI for managing Docker Compose stacks across multiple hosts.

One thing I wanted to keep from the start was the ability to work with normal Compose files. Your stacks stay as plain compose.yaml files on disk. You can edit them manually, keep them in Git or use docker compose directly without going through Dockmesh.

The server is a single Go binary with the UI embedded. Other hosts run a small agent that connects outbound to the server over mTLS, so you don't have to open incoming ports on every machine.

What it can do so far:

  • Manage Compose stacks across hosts, including deployments, rollbacks, Git-based deployments and moving stacks between hosts
  • Check for image updates, apply them and roll back if needed
  • Back up volumes, stacks and Dockmesh itself, with age encryption and support for local storage, SMB, SFTP, WebDAV and S3
  • Manage users with scoped roles, SSO (OIDC, SAML, LDAP, OAuth2) and 2FA
  • Send alerts for containers, hosts, disks, backups and certificates
  • Run vulnerability scans using Grype
  • Optionally handle reverse proxying and HTTPS through Caddy

There's also a hash-chained audit log, agent updates from the UI and a few other things. The UI is available in English and German.

Everything is open source (AGPL-3.0). There's no paid tier or separate edition.

Getting started

The easiest way to install it is:

curl -fsSL https://get.dockmesh.dev | sudo bash

The installer detects amd64/arm64, verifies the checksum and sets up a systemd service. If you'd rather inspect the script before running it (understandably), it's available in the repo. There's also a manual installation guide.

A few things worth mentioning

This is still a pre-1.0 project, so there's definitely more work to do. I test releases on lab VMs before publishing them, including server/agent upgrades, older-version upgrades, backup targets and SSO login.

I'm currently working on getting the initial server and host setup into the browser, along with an in-app updater.

I also want to be upfront about AI usage: parts of the code were written with AI assistance. I review and test changes before releasing them.

Dockmesh is mainly built for homelabs and small teams running anywhere from a few to a few dozen Docker hosts. It's not trying to replace Kubernetes.

I'd be interested to hear what you think, especially from people already managing Compose stacks across multiple machines. What's something your current setup does that you'd miss if you switched?

Repo: https://github.com/Dockmesh/dockmesh

Docs: https://dockmesh.dev


r/docker • • 7d ago

mongodb service gets killed when doing a docker stack deploy to another stack

5 Upvotes

i make remote deploys to my vps running docker swarm with the docker stack deploy command

i have multiple stacks for different applications deployed in my server, doing this, for some reason kills just the mongodb service; these are two different stacks, although they are connected to the same traefik network, that is the only thing they do share.

NAMEMODEIMAGEREPLICAS
xxx_dbreplicated0/1mongo:8.0.4

this is the my docker-stack file

notes:

  1. i use docker compose config before to pass the env vars and create a valid docker-stack.yaml file
  2. docker service update xxx_db fixes it, but i don't wanna be doing that always
  3. this just happens with the mongodb container, the other ones i have with postgres or nginx serving static sites are alright
services:
  db:
    image: mongo:8.0.4
    volumes:
      - mongodb_data:/data/db
      - ${PRODUCITON_HOME}/scripts/mongo-init.js:/docker-entrypoint-initdb.d/mongo-init.js:ro
    command: ["mongod", "--bind_ip_all"]
    secrets:
      - db-root-user
      - db-root-password
    environment:
      MONGODB_INITDB_ROOT_PASSWORD_FILE: /run/secrets/db-root-password
      MONGODB_INITDB_ROOT_USERNAME_FILE: /run/secrets/db-root-user
      GLIBC_TUNABLES: glibc.pthread.rseq=0
    networks:
      - db_net
    healthcheck:
      test:
        - CMD
        - mongosh
        - "mongodb://localhost:27017/admin"
        - "--eval=db.runCommand({ping:1})"
      retries: 3
      timeout: 5s
  server:
    secrets:
      - db-password
    environment:
      DB_PASSWORD_FILE: /run/secrets/db-password
      POOL_MIN_CONNS: ${POOL_MIN_CONNS}
      POOL_MAX_CONNS: ${POOL_MAX_CONNS}
      POOL_MAX_CONN_LIFETIME: ${POOL_MAX_CONN_LIFETIME}
      POOL_MAX_CONN_IDLE_TIME: ${POOL_MAX_CONN_IDLE_TIME}
      APP_PORT: ${APP_PORT}
      TOKEN_SECRET: ${TOKEN_SECRET}
      TOKEN_AUDIENCE: ${TOKEN_AUDIENCE}
      TOKEN_ISSUER: ${TOKEN_ISSUER}
      ACCESS_TOKEN_DURATION: ${ACCESS_TOKEN_DURATION}
      REFRESH_TOKEN_DURATION: ${REFRESH_TOKEN_DURATION}
      ORIGINS: ${ORIGINS}
      MAIL_HOST: ${MAIL_HOST}
      MAIL_PORT: ${MAIL_PORT}
      MAIL_USERNAME: ${MAIL_USERNAME}
      MAIL_PASSWORD: ${MAIL_PASSWORD}
      MAIL_SENDER: ${MAIL_SENDER}
    working_dir: /oooooooooooooo
    image: jjjjjjjjjjjj/oooooooooooooo:${GIT_HASH}
    networks:
      - db_net
      - traefik_proxy
    deploy:
      update_config:
        order: start-first
      labels:
        - "traefik.enable=true"
        - "traefik.http.routers.api-xxxxx.rule=Host(`xxx-xxxxxx.yyyyyyyyyyy.com`)"
        - "traefik.http.services.api-xxxxx.loadbalancer.server.port=5001"
volumes:
  mongodb_data:
networks:
  db_net:
  traefik_proxy:
    external: true
secrets:
  db-root-password:
    file: ./secrets/mongo-initdb-root-password.secret
  db-root-user:
    file: ./secrets/mongo-initdb-root-username.secret
  db-password:
    file: ./secrets/db-password.secret
  db-user:
    file: ./secrets/db-user.secret

this are the relevant log info i found

{
  "t": {
    "$date": "2026-11-14T15:54:30.114+00:00"
  },
  "s": "I",
  "c": "NETWORK",
  "id": 22943,
  "ctx": "listener",
  "msg": "Connection accepted",
  "attr": {
    "remote": "127.0.0.1:35898",
    "uuid": {
      "uuid": {
        "$uuid": "34b5dd72-5a66-4eff-9007-2fc5434528ab"
      }
    },
    "connectionId": 1,
    "connectionCount": 1
  }
}
{
  "t": {
    "$date": "2026-11-14T15:54:30.211+00:00"
  },
  "s": "I",
  "c": "NETWORK",
  "id": 51800,
  "ctx": "conn1",
  "msg": "client metadata",
  "attr": {
    "remote": "127.0.0.1:35898",
    "client": "conn1",
    "negotiatedCompressors": [],
    "doc": {
      "application": {
        "name": "mongosh 2.3.8"
      },
      "driver": {
        "name": "nodejs|mongosh",
        "version": "6.12.0|2.3.8"
      },
      "platform": "Node.js v20.18.1, LE",
      "os": {
        "name": "linux",
        "architecture": "x64",
        "version": "3.10.0-327.22.2.el7.x86_64",
        "type": "Linux"
      },
      "env": {
        "container": {
          "runtime": "docker"
        }
      }
    }
  }
}
{
  "t": {
    "$date": "2026-11-14T15:54:31.398+00:00"
  },
  "s": "I",
  "c": "NETWORK",
  "id": 22944,
  "ctx": "conn1",
  "msg": "Connection ended",
  "attr": {
    "remote": "127.0.0.1:35898",
    "uuid": {
      "uuid": {
        "$uuid": "34b5dd72-5a66-4eff-9007-2fc5434528ab"
      }
    },
    "connectionId": 1,
    "connectionCount": 0
  }
}
{
  "t": {
    "$date": "2026-11-14T15:55:09.294+00:00"
  },
  "s": "I",
  "c": "CONTROL",
  "id": 23377,
  "ctx": "SignalHandler",
  "msg": "Received signal",
  "attr": {
    "signal": 15,
    "error": "Terminated"
  }
}
{
  "t": {
    "$date": "2026-11-14T15:55:09.294+00:00"
  },
  "s": "I",
  "c": "CONTROL",
  "id": 23378,
  "ctx": "SignalHandler",
  "msg": "Signal was sent by kill(2)",
  "attr": {
    "pid": 0,
    "uid": 0
  }
}
{
  "t": {
    "$date": "2026-11-14T15:55:09.294+00:00"
  },
  "s": "I",
  "c": "CONTROL",
  "id": 23381,
  "ctx": "SignalHandler",
  "msg": "will terminate after current cmd ends"
}

full logs:
https://pastebin.com/36Uqyrgq


r/docker • • 7d ago

Docker Asks me to Install Rosetta?

0 Upvotes

Hi, so the title is self explanatory, I'm new to Mac OS, i'm using Mac air m5, and when i installed docker, it pushed me to download rosetta 2, which i think is older version of mac os and current one is tahoe, when i researched about it. it says support for rosetta will end in 2027...

what shall i do? is it recommended to install rosetta? or shall i just use homebrew to install cli version of docker?


r/docker • • 7d ago

DOCKER CLI VS GUI

0 Upvotes

Which one do you guys prefer?


r/docker • • 8d ago

should i use env vars or docker swarm secrets for stuff that is kinda a secret but not really? like db names, user db names, ports, etc

9 Upvotes

im not 100% if those don't count as stuff worth to keep inside secrets


r/docker • • 8d ago

Server is only accessible on host mode or when using container addresses

4 Upvotes

SOLVED, see here: https://www.reddit.com/r/docker/s/92gXpeXGTe. This post will self-destruct eventually.

Here is my docker-compose.yaml

name: tactics

services:
  server:
    container_name: server
    build:
      dockerfile: server.Dockerfile
    ports:
      - "8000:8000"
    networks:
      - backend

networks:
  backend:
    driver: bridge

and my server.Dockerfile

debian:bookworm-slim
ENV HOME=/root
ENV PATH="$PATH:$HOME/bin"
WORKDIR $HOME/bin
COPY Server.x86_64 Server.x86_64 ./
ENTRYPOINT ["/root/bin/Server.x86_64", "--headless", "--verbose"]

I create the Godot Server on a port, and create a Godot Client that connects to the same port.

If I use an address that refers directly to the container (the one shown by this https://stackoverflow.com/a/20686101) the connection is successful.

Or if I rewrite the compose to use host network mode, the connection is successful.

If I use any other address (0.0.0.0,, localhost, my public IP, my private IP), it times out.

Some suggestions have been to bind to 0.0.0.0, but I am not sure the effects of that or how it would be done in compose.

I am on an Ubuntu machine. I suppose I could also deploy to some cheap server farm. Any help is appreciated, including "don't worry about it and just use host / direct container address, here's why".

EDIT: btw I seemingly enabled br_netfilter as it was disabled, as suggested here: https://stackoverflow.com/a/60897412. Might be relevant. Didn't help though.


r/docker • • 8d ago

usb passthrough for esp32 on macos docker, anyone got it working?

3 Upvotes

so i recently moved from linux bazzite to an m2 macbook air and i've been trying to get my esp32 boards working inside docker devcontainers on vscode

the problem is macos can see my esp32-s3 just fine, esptool works and everything through /dev/cu.usbmodem but inside the devcontainer i can't access the usb at all

i use tool and script inside the container and i want them to be able to build, flash, read flash and monitor serial logs on multiple esp32 boards without me having to do everything manually. ideally jtag too. on bazzite this was literally just passing the device to docker and it worked

i've been looking around and found usb/ip, virtualhere, colima with qemu and orbstack. orbstack seems promising but it's proprietary and i'm kinda worried it'll stop being free someday. i'd prefer something open source if possible

i don't really wanna set up another full linux vm just for usb either, kinda defeats the point of using devcontainers in the first place

has anyone actually managed to get proper usb passthrough working on apple silicon? especially with esp32-s3 native usb serial/jtag? i'm looking for something that can handle flashing, resetting and monitoring repeatedly without randomly breaking

would appreciate hearing what actually works for you guys cause i've been going in circles with this for a while now


r/docker • • 9d ago

Mod Approved Guide - Use docker to operate legacy scanner hardware on Windows 11

Thumbnail
reddit.com
0 Upvotes

r/docker • • 11d ago

Sing-box in Docker always restarting

1 Upvotes

hello everyone and sorry for my English. I recently bought a VPS and install there Debian and docker from docs. And today i want to install sing-box in docker for my project, and i used command from Sing-box doc

docker run -d \

-v /etc/sing-box:/etc/sing-box/ \

--name=sing-box \

--restart=always \

ghcr.io/sagernet/sing-box \

-D /var/lib/sing-box \

-C /etc/sing-box/ run

And when i write in console, I always see

4d9eae7844b1 ghcr.io/sagernet/sing-box "sing-box -D /var/li…" 40 seconds ago Restarting (1) 10 seconds ago sing-box

How to solve it?


r/docker • • 11d ago

Matter server not starting

Thumbnail
reddit.com
4 Upvotes

i dont know how to continue, maybe someone can help me?

im running the latest version of HA as a docker container, which doesnt come with an integrated matter server. so according to documentation, i cloned the official matter server repository and wanted to run it again as a docker on the same host as the HA.

now i have the problem that the server doesnt start, it always fails with the eror below.

basically what it says is that creating the directory config"

asdmatterjs-server  | 2026-11-10 18:48:03.274 INFO   MatterServer         Command line: (no arguments)
matterjs-server  | 2026-11-10 18:48:03.281 INFO   MatterServer         Using storage drivers: kv=wal, blob=dir
matterjs-server  | 2026-11-10 18:48:03.294 INFO   ConfigStorage        Storage location: /data (Directory)
matterjs-server  | 2026-11-10 18:48:03.324 FATAL  MatterServer         Server failed to start /data/config: EACCES: permission denied, mkdir '/data/config'
matterjs-server  |   at async mkdir (node:internal/fs/promises:1571:10)
matterjs-server  |   at async NodeJsDirectory.mkdir (/app/node_modules/@matter/nodejs/src/fs/NodeJsDirectory.ts:83:9)
matterjs-server  |   at async NodeJsDirectory.lock (/app/node_modules/@matter/nodejs/src/fs/NodeJsDirectory.ts:91:9)
matterjs-server  |   at async DatafileRoot.#acquireRef (/app/node_modules/@matter/general/src/storage/DatafileRoot.ts:74:29)
matterjs-server  |   at async DatafileRoot.lock (/app/node_modules/@matter/general/src/storage/DatafileRoot.ts:64:20)
matterjs-server  |   at async WalStorageDriver.initialize (/app/node_modules/@matter/general/src/storage/StorageDriver.ts:264:26)
matterjs-server  |   at async WalStorageDriver.initialize (/app/node_modules/@matter/general/src/storage/wal/WalStorageDriver.ts:91:9)
matterjs-server  |   at async WalStorageDriver.create (/app/node_modules/@matter/general/src/storage/wal/WalStorageDriver.ts:52:13)
matterjs-server  |   at async StorageService.#openFilesystem (/app/node_modules/@matter/general/src/storage/StorageService.ts:273:29)
matterjs-server  |   at async ConfigStorage.open (/app/node_modules/@matter-server/ws-controller/src/server/ConfigStorage.ts:107:25)
matterjs-server  | 2026-11-10 18:48:03.386 NOTICE Runtime              Shutting down
matterjs-server exited with code 1 (restarting)