Suddenly cannot access listening TCP socket on host system from toolbox
Describe the bug
In my host system I have a user systemd unit in .config/systemd/user/[email protected] that just starts ssh -vCN %i as a Simple service and provides a socks5 proxy on 127.0.0.1:8075. I can see it if I run lsof -Pni :8075 on the host system.
This has worked ever since I started using Toolbox on Fedora silverblue in november 2022, and today suddenly in toolbox there is no such open socket. It's open and working in the host system, I can tell that the fedora-toolbox-37 container runs in NetworkMode host, but it's just not there in toolbox.
I've tried both restarting, stopping and deleting/re-creating the toolbox container with no success.
Steps how to reproduce the behaviour I assume this is specific to my setup and not actually reproducible but here are exactly the steps I'm taking after deleting the toolbox container.
toolbox createto create a default fedora-toolbox-37 container.lsof -Pni :8075to show if my socks5 proxy is listening.
Expected behaviour The output on my host system, and before today in toolbox, looks like this;
$ lsof -Pni :8075
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
ssh 5915 stemid 4u IPv6 59708 0t0 TCP [::1]:8075 (LISTEN)
ssh 5915 stemid 5u IPv4 59709 0t0 TCP 127.0.0.1:8075 (LISTEN)
Actual behaviour
No output at all in toolbox now.
Screenshots
Output of toolbox --version (v0.0.90+)
toolbox version 0.0.99.4
Toolbox package info (rpm -q toolbox)
toolbox-0.0.99.4-1.fc37.x86_64
Output of podman version
Client: Podman Engine
Version: 4.4.2
API Version: 4.4.2
Go Version: go1.19.6
Built: Wed Mar 1 12:22:59 2023
OS/Arch: linux/amd64
Podman package info (rpm -q podman)
podman-4.4.2-2.fc37.x86_64
Info about your OS
Fedora Silverblue 37.
Additional context
I feel like I'm going crazy here because I just tried running the regular fedora:37 image in --network host mode and it can't see the localhost socket either. I've literally been using this socket from toolbox for months! What is going on?! I'm assuming it's not toolbox related since podman has the same problem but I sure hope someone here has had the same situation.