r/docker • • 6h ago

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

11 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 • • 11h ago

Running Docker overlay2 on S3 Storage Using s3backer and ext4

2 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 • • 1d ago

Docker root question

5 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 • • 1d 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 • • 1d 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 • • 4d 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 • • 4d 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 • • 4d ago

DOCKER CLI VS GUI

0 Upvotes

Which one do you guys prefer?


r/docker • • 5d 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 • • 4d 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 • • 5d 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 • • 5d ago

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

Thumbnail
reddit.com
0 Upvotes

r/docker • • 7d 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 • • 8d 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)

r/docker • • 8d ago

Docker Engine 29.10.0 packaging changes (Alma,Oracle,Rocky Linux support)

7 Upvotes

Hi, many people were asking for a long time about official packages for AlmaLinux, Oracle Linux and Rocky Linux, and I'm happy to announce that they will finally be available in the upcoming Docker Engine 29.10.0!

29.10.0-rc.1 is already on the test channel, so you can try them now using the convenience script:

curl -fsSL [https://test.docker.com](https://test.docker.com) | sh

Or set up the repo yourself (replace rocky with alma or oracle):

sudo dnf -y install dnf-plugins-core
sudo dnf config-manager --add-repo https://download.docker.com/linux/rocky/docker-ce.repo
sudo dnf config-manager --set-enabled docker-ce-test
sudo dnf install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

This only applies to new installs. If you already installed Docker using the RHEL or CentOS repo, you'll keep getting packages from there until you switch the repo URL yourself:

sudo rm /etc/yum.repos.d/docker-ce.repo
sudo dnf config-manager --add-repo https://download.docker.com/linux/rocky/docker-ce.repo

There are also other changes related to static packages published on https://download.docker.com

Full changelog here: https://github.com/moby/moby/releases/tag/docker-v29.10.0-rc.1

Detailed installation instructions will be published on docs.docker.com after the GA release (which should be this week).

Please let us know if you encounter any issues!

Packaging issues: https://github.com/docker/packaging/issues/
Engine issues: https://github.com/moby/moby/issues/


r/docker • • 12d ago

The engineering team behind Bitnami has been laid off

250 Upvotes

r/docker • • 11d ago

Guidance please, on my first docker

5 Upvotes

I'm setting my first docker container, for SyncThing. The host is a Debian Trixie VM running in Proxmox. The VM has 2 virtual disks. One is the root file system and all its directories. I've created a directory "data01" for the second, bigger partition.

I've installed Docker, and all the tests show that it's ready to go to work, as far as I can tell. Systemctl status shows it ready.

The plan is to create a directory /data01/docker/syncthing and have it use that as the "home" for this container. Are there strict rules around where the compose YAML file needs to reside, or can I just put it in that folder? Does the file name have to be "compose.yaml"? I think the content will look something like this:

services:
  syncthing:
    image: lscr.io/linuxserver/syncthing:latest
    container_name: syncthing
    hostname: debian-syncthing
    environment:
      - PUID=0  # Run as root user
      - PGID=0  # Run as root group
      - TZ=America/New_York
    volumes:
      - /data01/docker/syncthing/config:/config 
      - /data01/docker/syncthing/data:/data 
    ports:
      - 8384:8384       # Web GUI
      - 22000:22000/tcp # Listening port for data sync (TCP)
      - 22000:22000/udp # Listening port for data sync (UDP)
      - 21027:21027/udp # Local discovery broadcasts
    restart: unless-stopped

Is there a better option than specifying the root user, or is that not relevant because it's going to be started at system boot?

Any advice appreciated.


r/docker • • 12d ago

Question over general docker usage/concept

4 Upvotes

Greetings,

I would like to share a problem that I'm facing with Docker, looking for some ideas.

In our company we've started to use docker hosted in an Azure DevOps cloud ubuntu machine, there we have an Azure self-hosted agent installed. We work only with firmware projects and this is our build server. We have this setup for 3 years.

Usually, I generate the docker images on demand according with the project requirements.
In our firmware projects hosted in git we have a yaml pipeline configuration where we set the image tag so that the proper container can be raised to process the build.

We have a requirement from safety standards (we must keep the project artifacts/infrastructure from 10 to 15 years), because of that I keep all the dependencies I need to reproduce/re-create an image as debian installers (for offline installation). I've created a script which runs prior the build process, which creates a yaml manifest containing all the image packages and include this manifest also in the image (at /etc/manifest.yaml) for runtime check. Then it's possible to verify the content via the manifest hash. Examples of dependencies we have are cmake, unit test tools, static code analyzer, and so on.
We decided to keep everything in a single image because most of the tools require the compiler, so that the image complexity keeps lower as possible.

As we have different projects using the same images, we keep the Dockerfiles under version control, where the image name is the compiler version (the most significant dependency for our projects), something like this:

docker-<compiler>-<version>
  ubuntu-24.04
    Dockerfile
    build-image.sh
    manifest.yaml
  ubuntu-22.04
    Dockerfile
    ...

When a new image is generated, I tag the commit with the same tag I use in the container (e.g commit tag ubuntu24.04-v1.0-0, for a created container named gcc-13.3.0:ubuntu24.04-v1.0-0).

As our concept is based on tags, and the docker tags are not the most reliable thing in the world, I keep also the tagged image name as a LABEL within the image.

At this point I ask myself if we are going in the right direction and the increased complexity in the toolchain management is because of the concept we've decided to go for, or if it's just what we have to do in order to be compliant with such safety requirements. Or even I ask if we are drifting from the docker concept or using the tool in a wrong way.

I would really like to hear opinions, especially from other colleagues in similar situation.

Thanks in advance.

Note: I know that I can save the image in a registry, in parallel I'm trying to find solutions (if possible) to reduce storage costs (each image ~20GB).


r/docker • • 12d ago

What Docker containers can you recommend that I install on my Debian Home Server?

Thumbnail reddit.com
0 Upvotes

r/docker • • 12d ago

NetAlertX Problems at Initially Starting the docker Container

2 Upvotes

[SOLVED] - The workaround is in the 1st reply

I'm starting with the docker compose setup of NetAlertX using the guide on the github page. It's a Rocky Linux 9.7 system that has been running a couple other docker containers without any issues.

The error message isn't too helpful:

[dockeruser@rocky-mini-01 NetAlert]$ docker compose up
Attaching to netalertx
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: sysctl "net.ipv4.conf.all.arp_announce" not allowed in host network namespace

I've been using docker for a while, but I am about an intermediate user at best. I can't tell if there are multiple errors listed here or just 1.

The last part is plain (runc create failed: sysctl "net.ipv4.conf.all.arp_announce" not allowed in host network namespace), but none of the remedies solve it. The compose.yaml file already has the "NET_ADMIN" and "network_mode: ${NETALERTX_NETWORK_MODE:-host}" and the entry for

sysctls:
net.ipv4.conf.all.arp_ignore: 1
net.ipv4.conf.all.arp_announce: 2

I've tried using:

sudo sysctl -w net.ipv4.conf.all.arp_ignore=1
sudo sysctl -w net.ipv4.conf.all.arp_announce=2

I've tried running the docker compose command as the dockeruser and root.

Literally, the only thing I changed from the NetAlertX compose file with the path:

# Example custom local folder called /home/user/netalertx_data

- type: bind
source: /mnt/disk/docker/NetAlertX/netalertx_data
target: /data
read_only: false

Any clues?


r/docker • • 12d ago

Create a docker image from dockerfile?

0 Upvotes

I got a dockerfile here that is sitting in my files but for some reasons docker cannot build an image out of it as it keep saying "failed to build: failed to solve: failed to read dockerfile: open Dockerfile: no such file or directory"

# For more information, please refer to https://aka.ms/vscode-docker-python
FROM python:3.13


EXPOSE 8501


# Keeps Python from generating .pyc files in the container
ENV PYTHONDONTWRITEBYTECODE=1


# Turns off buffering for easier container logging
ENV PYTHONUNBUFFERED=1


# Install pip requirements
COPY requirements.txt .
RUN python -m pip install -r requirements.txt


FROM ollama/ollama
RUN ollama pull nomic-embed-text
RUN ollama pull qwen2.5:0.5b 



WORKDIR /app
COPY . /app


# Creates a non-root user with an explicit UID and adds permission to access the /app folder
# For more info, please refer to https://aka.ms/vscode-docker-python-configure-containers
RUN adduser -u 5678 --disabled-password --gecos "" appuser && chown -R appuser /app
USER appuser


# During debugging, this entry point will be overridden. For more information, please refer to https://aka.ms/vscode-docker-python-debug
CMD ["ollama", "serve","gunicorn", "--bind", "0.0.0.0:8501", "-k", "uvicorn.workers.UvicornWorker", "local_rag:app"]

How do I build an image out of it. I wrote the file in vscode


r/docker • • 13d ago

Any Docker Recommendations?

34 Upvotes

I just got into Docker for the first time, I know some of the basic fundamentals. But is there any recommendations or courses you took to help you understand Docker please I will really appreciate your recommendation.


r/docker • • 14d ago

my Docker backup worked but my recovery plan didn’t

11 Upvotes

I thought my backup setup was fine. the Compose file was in Git and the vm was backed up. Then I tried restoring everything instead of just assuming it would work. I started with easy test and restored my serverspace vm backup to a second server. The app came back with the database and uploads. Then I created a blank ubuntu vm, cloned the repo and ran docker compose up d. Every container was healthy but the app was empty. The Compose file could rebuild the stack, not the data.

I’ve since added separate postgres dumps and copies of the uploads and secrets outside the VM. The provider backup is still my quick recovery option but at least I can now rebuild elsewhere if I need to. For those who test their backups regularly how ofen do you actually rebuild everything on a clean vm? I need help


r/docker • • 14d ago

Contact to marketing or event team in EU

0 Upvotes

I am organizing an event and need a contact to marketing or event team, responsible for EMEA or more specific CEE region. Any ideas?