Public bug reported:
I run a Gitea server on an Ubuntu server 24.04.3 LTS using Podman and
docker-compose. This setup has worked fine for several years.
Today I rebooted the host as Ubuntu asked for it due to a kernel update.
As I had updated the host recently, the kernel update was the only
difference between the before and after reboot.
After the reboot, DNS stopped working for the two containers started by
docker-compose. Another podman container is running on the same host
with Artifactory JCR - this container works fine. I haven't changed
anything on the host except for the reboot.
I run Logwatch on the host, and it reports the following change since
the last reboot:
--------------------- dpkg status changes Begin
------------------------
Installed:
linux-headers-6.8.0-87-generic:amd64 6.8.0-87.88
linux-headers-6.8.0-87:all 6.8.0-87.88
linux-image-6.8.0-87-generic:amd64 6.8.0-87.88
linux-modules-6.8.0-87-generic:amd64 6.8.0-87.88
linux-modules-extra-6.8.0-87-generic:amd64 6.8.0-87.88
linux-tools-6.8.0-87-generic:amd64 6.8.0-87.88
linux-tools-6.8.0-87:amd64 6.8.0-87.88
Upgraded:
linux-generic:amd64 6.8.0-86.87 => 6.8.0-87.88
linux-headers-generic:amd64 6.8.0-86.87 => 6.8.0-87.88
linux-image-generic:amd64 6.8.0-86.87 => 6.8.0-87.88
linux-libc-dev:amd64 6.8.0-86.87 => 6.8.0-87.88
linux-tools-common:all 6.8.0-86.87 => 6.8.0-87.88
Removed:
linux-headers-6.8.0-85-generic:amd64 6.8.0-85.85
linux-headers-6.8.0-85:all 6.8.0-85.85
linux-image-6.8.0-85-generic:amd64 6.8.0-85.85
linux-modules-6.8.0-85-generic:amd64 6.8.0-85.85
linux-modules-extra-6.8.0-85-generic:amd64 6.8.0-85.85
linux-tools-6.8.0-85-generic:amd64 6.8.0-85.85
linux-tools-6.8.0-85:amd64 6.8.0-85.85
---------------------- dpkg status changes End -------------------------
The Docker compose in question is here:
version: "3"
networks:
gitea:
external: false
services:
server:
image: gitea/gitea:1.25.1
container_name: gitea
environment:
- USER_UID=1000
- USER_GID=1000
restart: always
networks:
- gitea
volumes:
- /data/gitea/data:/data
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
ports:
- "3000:3000"
- "2222:22"
depends_on:
- db
db:
image: mariadb:10.6
container_name: gitea-db
restart: always
networks:
- gitea
volumes:
- /data/gitea/mysql:/var/lib/mysql
Neither internal nor external DNS works. If I change the Gitea
configuration to point to the IP address of the database, it starts just
fine. However, Gitea still cannot make DNS lookups and hence cannot
notify the build system about changes, etc.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: podman 4.9.3+ds1-1ubuntu0.2
ProcVersionSignature: Ubuntu 6.8.0-87.88-generic 6.8.12
Uname: Linux 6.8.0-87-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Nov 7 15:49:12 2025
InstallationDate: Installed on 2025-06-20 (140 days ago)
InstallationMedia: Ubuntu-Server 24.04.2 LTS "Noble Numbat" - Release amd64
(20250216.2)
ProcEnviron:
LANG=en_GB.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
SourcePackage: libpod
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2130887
Title:
DNS stopped working in Podman after kernel update
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2130887/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
