Open 0rzech opened 1 month ago
The mentioned steps are not enough to reproduce the exact error (requires also installing quarkus), but the java.net.UnknownHostException: toolbox
suggests there is some kind of change to the network settings of the toolbox container, not specific to Java/Quarkus.
In the test below, I think we can see the same problem just by using the default programs included in the toolbox image.
[user@toolbox ~]$ cat /etc/fedora-release
Fedora release 39 (Thirty Nine)
[user@toolbox ~]$ cat /etc/hostname
toolbox[user@toolbox ~]$
[user@toolbox ~]$ hostname -s
toolbox
[user@toolbox ~]$ hostname -f
toolbox
[user@toolbox ~]$ curl -v http://toolbox
* processing: http://toolbox
* Trying [fe80::fae3:66bc:a805:3bc6]:80...
* Trying 10.97.21.241:80...
[user@toolbox ~]$ cat /etc/fedora-release
Fedora release 40 (Forty)
[user@toolbox ~]$ cat /etc/hostname
toolbox[user@toolbox ~]$
[user@toolbox ~]$ hostname -s
toolbox
[user@toolbox ~]$ hostname -f
hostname: Name or service not known
[user@toolbox ~]$ curl -v http://toolbox
* Could not resolve host: toolbox
* Closing connection
curl: (6) Could not resolve host: toolbox
Fedora Linux 40.20240512.0 (Silverblue)
toolbox version 0.0.99.5
toolbox-0.0.99.5-8.fc40.x86_64
There is a difference in how fedora-toolbox:39
and fedora-toolbox:40
set their FQDN hostname, as hostname -f
unexpectedly fails in 40. Then, I am using curl
just to check the DNS resolution, as the toolbox doesn't have dig/nslookup/etc. Didn't notice any interesting changes to /etc/hosts
or /etc/resolv.conf
, but there must be something else going on.
There are a number of other Issues/PRs in this repo about DNS and hostname changes, but I'm unclear which could be related or not.
There are some changes to /etc/resolv.conf symlink in #1410, could they be related? I can reproduce this issue on my system -
toolbox version 0.0.99.5
toolbox-0.0.99.5-11.fc40.x86_64
Fedora Linux 40 (Workstation Edition)
I've been having trouble with X11 programs running in Toolbox containers in Kinoite. The whole KDE desktop (wayland) hangs for several seconds when an X-application (especially Wrye Bash, https://github.com/wrye-bash/wrye-bash, but also vim) opens dialogs or context menus.
Running "sudo hostname localhost" in the toolbox container resolved the issue and X-applications seem to run fine now without hanging the rest of the desktop.
Describe the bug
Quarkus application runs fine when started inside
fedora-toolbox:39
container. But insidefedora-toolbox:40
, ajava.net.UnknownHostException: toolbox
gets thrown.Steps how to reproduce the behaviour
toolbox create
.sudo dnf install --setopt=install_weak_deps=False java-21-openjdk-devel
inside container.quarkus dev
orquarkus test
inside container.Expected behaviour
Java should not throw the aforementioned exception.
Actual behaviour
Upon starting Quarkus application, the following warning is printed and exception is thrown:
Screenshots
N/A
Output of
toolbox --version
(v0.0.90+)toolbox version 0.0.99.5
Toolbx package info (
rpm -q toolbox
)toolbox-0.0.99.5-8.fc40.x86_64
Output of
podman version
Podman package info (
rpm -q podman
)podman-5.0.3-1.fc40.x86_64
Info about your OS
Fedora Silverblue 40
Additional context
Running
podman system reset
did not help.