I can't access the podman mapped ports #20755

jiawen94 · 2023-11-23T03:20:52Z

jiawen94
Nov 23, 2023

OS:debian 11.2

Version:      3.0.1
API Version:  3.0.0
Go Version:   go1.15.15
Built:        Thu Jan  1 08:00:00 1970
OS/Arch:      linux/amd64

I have a podman container, port map is

podman port my_superset
8088/tcp -> 0.0.0.0:9999

last week I accidentally deleted /lib directory, then I recovery it by copy /lib dir (from another new debian 11.2) to this host.
when I started podman ,it showed missing dbus:

podman start my_superset
Error: OCI runtime error: unable to start container "51d0be9c6634e0adb83127b8a8d69abd39844b1143b552fec34091bf4f7ed8fa": cannot open sd-bus: Connection refused”

I reinstall dbus apt reinstall dbus. then podman and container can be run successfully.
However, I cant access the 9999 port via other host. I can only access 9999 port via localhost

 curl  localhost:9999
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>Redirecting...</title>
<h1>Redirecting...</h1>
<p>You should be redirected automatically to target URL: <a href="/superset/welcome/">/superset/welcome/</a>.  If not click the link.#

There is no selinux,iptables or firewalld limit on port 9999.
The problem occurs after accidentally deleting and restoring the /lib directory
I have no idea.

jiawen94 · 2023-11-23T03:29:03Z

jiawen94
Nov 23, 2023
Author

ss -tnal|grep 9999
LISTEN 0      65535        0.0.0.0:9999       0.0.0.0:*

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

I can't access the podman mapped ports #20755

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

I can't access the podman mapped ports #20755

Uh oh!

Uh oh!

jiawen94 Nov 23, 2023

Replies: 1 comment

Uh oh!

jiawen94 Nov 23, 2023 Author

jiawen94
Nov 23, 2023

jiawen94
Nov 23, 2023
Author