Can't resolve host toolbox inside fedora-toolbox:40 container
#1498
Comments
0rzech
changed the title
fedora-toolbox:40 container causes java.net.UnknownHostException: toolboxfedora-toolbox:40 container causes java.net.UnknownHostException: toolbox
|
The mentioned steps are not enough to reproduce the exact error (requires also installing quarkus), but the In the test below, I think we can see the same problem just by using the default programs included in the toolbox image. fedora-toolbox:39 (works)[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...fedora-toolbox:40 (doesn't work)[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: toolboxEnvironmentFedora Linux 40.20240512.0 (Silverblue)
toolbox version 0.0.99.5
toolbox-0.0.99.5-8.fc40.x86_64There is a difference in how 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. |
0rzech
changed the title
fedora-toolbox:40 container causes java.net.UnknownHostException: toolboxtoolbox inside fedora-toolbox:40 container
|
There are some changes to /etc/resolv.conf symlink in #1410, could they be related? |
|
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. |
|
This issue also seems to result in commands such as A workaround is to add |
|
I am no longer able to reproduce this issue after upgrading to Fedora Silverblue 41 w/ Toolbox v0.1.0. EnvironmentFedora Linux 41.20241109.0 (Silverblue)
toolbox-0.1.0-1.fc41.x86_64
podman-5.2.5-1.fc41.x86_64Toolbox - Fedora 40[user@toolbx ~]$ cat /etc/fedora-release
Fedora release 40 (Forty)
⬢ [user@toolbx ~]$ cat /etc/hostname
toolbx
⬢ [user@toolbx ~]$ hostname -s
toolbx
⬢ [user@toolbx ~]$ hostname -f
toolbx
⬢ [user@toolbx ~]$ curl -v http://toolbx
* Host toolbx:80 was resolved.
* IPv6: fe80::f91d:xxxx:xxxx:179c, 2601:182:b01:8901:xxxx:xxxx:3718:6618
* IPv4: 10.90.21.237Toolbox - Fedora 41⬢ [user@toolbx ~]$ cat /etc/fedora-release
Fedora release 41 (Forty One)
⬢ [user@toolbx ~]$ cat /etc/hostname
toolbx
⬢ [user@toolbx ~]$ hostname -s
toolbx
⬢ [user@toolbx ~]$ hostname -f
toolbx
⬢ [user@toolbx ~]$ curl -v http://toolbx
* Host toolbx:80 was resolved.
* IPv6: fe80::f91d:xxxx:xxxx:179c, 2601:182:b01:8901:xxxx:xxxx:3718:6618
* IPv4: 10.90.21.237 |
Describe the bug
Quarkus application runs fine when started inside
fedora-toolbox:39container. But insidefedora-toolbox:40, ajava.net.UnknownHostException: toolboxgets thrown.Steps how to reproduce the behaviour
toolbox create.sudo dnf install --setopt=install_weak_deps=False java-21-openjdk-develinside container.quarkus devorquarkus testinside 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.5Toolbx package info (
rpm -q toolbox)toolbox-0.0.99.5-8.fc40.x86_64Output of
podman versionPodman package info (
rpm -q podman)podman-5.0.3-1.fc40.x86_64Info about your OS
Fedora Silverblue 40Additional context
Running
podman system resetdid not help.The text was updated successfully, but these errors were encountered: