I'm using OpenMediaVault 7 (Debian 12) and I would have gone to OpenMediaVault for support first except that the subreddit has died and the forums constantly return 500 errors for me.

I have the docker compose plugin installed so I just make a compose file in the GUI and everything runs fine, except that my containers cannot resolve FQDNs. I have put the DNS flag in my containers:

dns:
- 8.8.8.8

My containers are not using the default bridge network but rather the bridge network that is created separately for each container with compose.

I can run

docker run --rm curlimages/curl:latest curl 1.1.1.1

And it returns a successful request. BUT if I run the same request with google.com instead of an IP, it fails to resolve, even if I add the --dns flag in the run command.

The /etc/resolv.conf internal to the container(s) says the nameserver is 127.0.0.11

The /etc/resolv.conf on the host machine says 127.0.0.53 is the nameserver.

Resolvectl says that the DNS server on enp3s0 is 8.8.8.8

I have set /etc/docker/daemon.json to have both 8.8.8.8 and 1.1.1.1 as nameservers.

I have set my DNS= in /etc/systemd/resolved.conf to 8.8.8.8.

The host has name resolution.

I just want to be able to run my game servers. Please help me, I am falling into insanity.

My Plex container was compromised in the recent Plex2Shell attack. I’ve managed to stop the malicious processes and set up a fresh, updated Plex container, but I cannot get the original infected container deleted.
I’m running Docker 24 on a Synology DS423+ with Btrfs. The old container has been stuck in removing for days, with PID 0. I’ve tried restarting Docker and even rebooting the entire NAS, but neither fixed it.
From the diagnostics, Docker seems to be getting stuck traversing a massive /run/plex-temp directory in the old container’s writable layer. It looks similar to this Docker issue: https://github.com/moby/moby/issues/42973
Has anyone dealt with this before? Is there a way to safely force the container and its writable layer to be deleted without affecting my other containers or media?
I’ve spent days on this and would really appreciate any suggestions beyond restarting Docker or the NAS, since I’ve already tried both.

I just started a docker dedicated server on my NAS this week using the mornedhels/enshrouded-server image. It was working great until the enshrouded patch today. I tried updating the image and rerunning a couple times, even trying proton vs wine types and running it again. The server shows up in game every time with the “Version Mismatch. The build version of this server is older than yours. The owner of this server needs to update it to the latest version.”

The image was updated about an hour ago so it should be ready for the patch but I can’t seem to get it updated. Has anyone else had to deal with this type of issue?

Other notes:
Didn’t see any errors in the Logs

I’m running Docker on Debian and Ubuntu. After years, I tried Docker Desktop on Windows. Why does it show 15.65% / 3200% (32 CPUs available)? Why does it count 1 CPU/thread as 100%?

To use SSL in a Docker website with Apache, I have to provide .key and .crt files created with openssl req. Am I supposed to copy into the containers the same pair of files or create a different pair for each? Does Traefik matter here?

Docker-compose --version says it isn't installed, but I used docker-compose up -d two days ago?

Any ideas? I don't want to install compose through terminal if that will conflict with the plugin.

Thanks!

Edit: return docker-compose --version is actually -bash: docker-compose: command not found

Trying to get Immich to upload photos to an external hard drive. I am using Docker for Windows. I have tried putting /mnt/d/ImmichLibrary in the ENV file and then it creates a folder in the same location as the ENV file (c drive).

Any help appreciated!!

I have some critical containers on my home server (mainly Home Assistant and friends) that I can't live without. My whole home and life is dependent on them, lol. I already run RAID1c3 BTRFS, dual UPS and have a backup system in place. But it's impossible to eliminate every possible source of disasters. Especially on a modest budget.

I have an old Intel NUC to use as a shadow server for emergency failover.

1. Docker Swarm - doesn't handle storage

2. Kubernetes - apparently can handle storage but I'm told it's difficult.

3. Bash scripts, SSH, BTRFS snapshots etc. - I'm pretty good at this stuff so it seems like the default approach. Wake the shadow up, update it, test it and send it back to sleep every interval.

What's the right answer?

I downloaded and ran Ganymede (https://github.com/zibbp/ganymede) a few months back, it has since updated but I have no idea if there’s a way to update it without starting from scratch as a new application?

Using Docker Desktop on Windows.

I'm new to Docker Desktop, so sorry for my ignorance. I've been able to start/stop docker desktop using "docker desktop stop" and "docker desktop start". The problem with "docker desktop start" is that while it does start docker desktop, docker desktop only lives as long as the terminal that started it is up. As soon as I kill my Terminal, Docker Desktop just dies.

The reason I pretty much need this, is because I only have 16 GB RAM, and Windows steals a quarter of it, while Docker Desktop steals half. I'm left with like a quarter of my RAM (which my browser wants to eat), so I'm left with almost no RAM left, which forces me to kill docker desktop (killing only containers isn't enough, since the linux vm itself is the main problem), while I actually use my pc. I tend to forget to boot up docker desktop again when leaving the pc, so a way to launch it persistently via ssh would be great. But that turned out to be harder than expected.

I develop against Kube, Swarm and Compose stacks and got tired of port mappings and /etc/hosts edits, so I built plug. You prefix your usual command:

plug -s my-api:8080:3000 npm run start:dev

- Your process resolves cluster names (postgres, my-service:8080) as if it were a container. No code or proxy config, any runtime.

- The cluster reaches your process as my-api:8080. The name doesn't need to exist yet. If a deployed service already owns it, plug parks it for the session and restores it on exit.

- On a takeover it also inherits the service's environment, secret/config files and volumes (mounted over SMB, no FUSE).

- Docker, Compose, Swarm, Kubernetes. Linux, macOS, Windows. One agent container; developers only need the cluster's address.

Free, source-available. mirrord and Telepresence do similar things for Kubernetes; there's a side-by-side in the docs, including where they're ahead.

Repo: https://github.com/softwarity/plug

Docs: https://softwarity.github.io/plug/

I'd really like feedback from people: what would make this useful for your workflow?

PS: I tried to message the mods, but I get an error message.

https://youtu.be/2f0LUg5_GvQ 🎦

With cloud costs and bandwidth going up, I’m seeing more teams start to actually care about container size. Tried every way I could think of how to build a Java Docker image and compared the sizes.

Anyone else optimizing for size? or your team just never looks at the cloud bill?

This is my first time using docker and I want to download oracle database (version 19 to be exact) on my mac and use it for my university assignment. As soon as I created an image, I received an error stated that "ERROR: failed to build: failed to solve: process "/bin/sh -c chmod ug+x \"$INSTALL_DIR\"/*.sh &&     sync &&     export CV_ASSUME_DISTID=OL7 &&     \"$INSTALL_DIR\"/\"$INSTALL_DB_BINARIES_FILE\" $DB_EDITION" did not complete successfully: unable to find user oracle: no matching entries in passwd file". I tried many ways still unsuccesfull.

Hi everyone,

We are testing a local background service running on client laptops. During peak context processing, memory spikes can risk pushing the host OS into swap death.

We are configuring container resource limits (--memory, --memory-swap, cgroups v2) to isolate the local execution daemon from the rest of the host system.

For those deploying background containers on desktop client endpoints: what memory overhead buffer do you leave for the host OS to prevent hard freezes when a container hits its hard limit?

Context: Architectural query regarding container limits on client endpoints.

Hi everyone,

I recently downloaded and installed Docker Desktop from the official Docker website on my MacBook Air M5. However, after the installation, when I try to open Docker Desktop, nothing happens. The application doesn't launch or show any visible response.

Has anyone experienced this issue on an M5 MacBook? I would appreciate any suggestions or troubleshooting steps to get Docker Desktop working.

Os: 26

Thanks in advance for your help!

So I have a tool packaged on GHCR and the download counts have been growing at a steady clip, with every release going up , moving roughly at a 200-300 a day rate… last release was about 5000 users in 3 weeks, latest release nearly 8000 in 3 weeks….but I’ve read that some docker management tools can ping GHCR checking for updates and end up creating a false “download” count … does anyone have a bead on this? How reliable are these download counts?

I just noticed that my docker container hasn't updated in months. Did some research and realized I was running from cache. Tried adding pull_policy: always to my compose file, but got this error: docker: Error response from daemon: pull access denied for plex, repository does not exist or may require 'docker login'

manually ran: docker pull linuxserver/plex:latest This worked.

How do I update the compose to auto-pull latest?

I’m genuinely sick to my stomach while typing this.
For the past few months, I’ve been consistently working on a system that helps run my business every single day. Every line of code, every hour, every late night, and all those days of frustration went into building something that my business relies on. Months of hard work, all completely wiped because of Docker.

Earlier today, I noticed Docker was constantly using around 8GB of RAM, which I thought was very odd considering the size of my system. So I went into Docker’s settings to reduce the maximum RAM usage. While I was there, I noticed other settings for CPU usage and disk limits, so I decided to reduce those as well.

I clicked “Apply & Restart”, and when Docker loaded back up, everything was gone. Not a single container was there. At first, I thought it was just some sort of bug, but after digging deeper, I found out that reducing the disk limit actually deletes the entire Docker disk image, including all your containers, volumes, and stored data.

The worst part is I received absolutely no warning. No confirmation, no pop-up telling me my data would be permanently deleted. Nothing. I simply changed what I thought was a resource limit, clicked apply, and lost months of work in seconds.

I genuinely cannot understand how something like this is allowed to happen. How can changing a setting as simple as a disk limit completely wipe everything without even warning the user about what’s going to happen?

This is a warning to all of you please don’t make the same mistake I’ve made. I’m in tears and speechless. How is a company allowed to do this.

EDIT: Just to clarify, I wasn’t storing everything inside the container. I was using a Docker named volume mounted to /home/node/.n8n.
I understand I should’ve had more recent external backups, that’s on me. But my issue is that I received absolutely NO warning that reducing the disk limit would permanently delete everything. I simply clicked Apply & Restart, and months of work were gone. That’s the whole point of this post.

EDIT 2: Update for anyone who finds this later. I recovered most of my work from a backup on another drive from a couple of weeks ago. Lessons learnt:

1. On Docker Desktop (Mac), named volumes live inside Docker’s virtual disk. Reducing the disk limit can wipe that disk entirely, volumes included. I didn’t get a confirmation prompt.

2. Bind-mount important data to a real folder on your machine instead of relying on named volumes.

3. Automate backups to a separate drive or cloud.

I still think a destructive setting like this deserves a warning, but yes, backups were on me. Thanks to everyone who gave genuinely useful advice.

Rosetta 2 is to be partially discontinued in macOS 28, How will docker work?

Hi!

I have an open source pet project related to networks.
Users asked me to create an official Docker image, but I’ve never worked with Docker before.
Fortunately, some kind person made (or vibe coded, doesn't matter) a Dockerfile and docker-compose.yml for us.

But I want to figure it out myself, and here are some things that I don’t quite understand:

- our tool can receive data from the network either in the traditional way (using sockets) or via pcap; this is user-configurable.
Different users use different capture methods. As far as I understand, it would be better to create two images - one normal and the other privileged, with access to the host network.
Or is that not the standard practice?

- even though we can capture data using pcap, the tool still runs as a non-root user. We use setcap to achieve this.
The kind person who created the Dockerfile for us included this line:
RUN useradd -u 53842 -rlM -d /nonexistent -s /usr/sbin/nologin user
I asked why UID 53842 was chosen, and he replied that it was to ensure the UID wouldn't conflict with other users.
Is this standard practice, or are there other ways to do it?

- The tool generates database data as it runs. Literally .sql files.
Periodically, it launches an external script that feeds these files to the psql utility, sending the data to PostgreSQL.
We've now added support for ClickHouse, and we might even add export to InfluxDB or MariaDB.
Sure, we could keep everything in a single large image.
However, I’m a bit concerned that the 'clickhouse-client' is orders of magnitude larger than the tool itself; if we add support for other databases, the image will become massive.
Is this normal? Is this how it's usually done?
Or would it be better to do it differently?

- The tool sometimes launches other external scripts. These scripts typically generate alerts, send messages via email, instant messengers, etc.
In other words, it invokes curl, a mail client, or other utilities that we definitely don't want to package inside the container.
I’ve read about two ways to launch external scripts from Docker: using ssh and named pipes. It looks a little creepy.
Are there other ways to run an external script on the host or in another container?

- In addition to the main tool, the kit includes several other small utilities. They all use the same data (shared files).
I don't think there would be any issues keeping them in a single shared image.
But perhaps I'm mistaken.
What is the standard practice in the Docker world?

Thanks in advance!

Hello, I'm trying to learn how to use IPV6 at home. IPV6 is enabled on my network and my vlans.

I have updated the daemon.json file per Docker's instructions.

{
  "ipv6": true,
  "fixed-cidr-v6": "2001:1234:5678::/64"
}

I have stopped all containers, removed the old IPV4 macvlan networks, re-added them as IPV4 & IPV6 networks, Portainer seems to think the two I've done are correct.

sudo docker network create -d macvlan --ipv6 \
--subnet=10.0.10.0/24 --gateway=10.0.10.1 \
--subnet=2001:1234:5678:10::/64 --gateway=2001:1234:5678:10::1 \
-o parent=eth0.10 macvlan10

sudo docker network create -d macvlan --ipv6 \
--subnet=10.0.20.0/24 --gateway=10.0.20.1 \
--subnet=2001:1234:5678:20::/64 --gateway=2001:1234:5678:20::1 \
-o parent=eth0.20 macvlan20

I've added IPV6 addresses and IPV6 enable in my Docker Compose/Portainer Stacks, but don't seem to have something correct here.

services:
  pihole:
    cap_add:
      - SYS_TIME
      - SYS_NICE
    container_name: pihole01
    environment:
      FTLCONF_dns_listeningMode: 'all'
      FTLCONF_dns_upstreams: '1.1.1.1;1.0.0.1'
      FTLCONF_webserver_api_password: 'SuperSecretPassword'
      TZ: 'America/Detroit'
    hostname: pihole01
    image: pihole/pihole:latest
    mac_address: 00:10:00:10:00:04
    networks:
      macvlan10_network:
        ipv4_address: 10.0.10.4
        ipv6_address: 2001:1234:5678:10::4
    ports:
      - "53:53/tcp"
      - "53:53/udp"
      - "80:80/tcp"
      - "123:123/udp"
      - "443:443/tcp"
    restart: unless-stopped
    volumes:
      - pihole01:/etc/pihole

networks:
  macvlan10_network:
    enable_ipv6: true
    external: true
    name: 'macvlan10'

volumes:
    pihole01:
      external: true

Any ideas?