Podman remoteSocket not enabled on ubuntu 24.04 with version 4.9.3

[kishorekumar-anchala]

Issue Description

The socket should be enabled by default .

version : Podman 4.9.3

Could you help why this service not enabled with 4.9.3 ?

Steps to reproduce the issue

NA

Describe the results you received

The socket not enabled by default .

version : Podman 4.9.3

Describe the results you expected

The socket should be enabled by default .

version : Podman 4.9.3

podman info output

The socket should be enabled by default .

version : Podman 4.9.3

Podman in a container

Yes

Privileged Or Rootless

None

Upstream Latest Release

No

Additional environment details

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

[rhatdan]

Why should it? Podman works perfectly on a Linux machine without a remote socket. It is different then Docker.

[kishorekumar-anchala]

Hi @rhatdan - it works fine , but compare to other versions (lower than 4.9.3) remotesocket was enabled . with the latest version that service is disabled it impacting the customers .

is there any reason why this service is disabled by default on containers?

[baude]

unless I am misreading this, that is decided by the distribution itself. Perhaps @siretart could provide insight but otherwise (again, if I am understanding your issue) this is an Ubuntu thing.

[afbjorklund]

It seems the system daemon is enabled, but the user daemon is disabled?

● podman.socket - Podman API Socket
     Loaded: loaded (/usr/lib/systemd/system/podman.socket; enabled; preset: enabled)
     Active: active (listening) since Wed 2025-01-15 17:44:23 CET; 1min 44s ago

○ podman.socket - Podman API Socket
     Loaded: loaded (/usr/lib/systemd/user/podman.socket; disabled; preset: enabled)
     Active: inactive (dead)

As far as I know, systemd enables everything - unless the distribution presets.

---

EDIT: no big mystery there, it is done by the postinst

        # was-enabled defaults to true, so new installations run enable.
        if deb-systemd-helper --quiet was-enabled 'podman.socket'; then
                # Enables the unit on first installation, creates new
                # symlinks on upgrades if the unit file has changed.
                deb-systemd-helper enable 'podman.socket' >/dev/null || true
        else
                # Update the statefile to add new symlinks (if any), which need to be
                # cleaned up on purge. Also remove old symlinks.
                deb-systemd-helper update-state 'podman.socket' >/dev/null || true
        fi

On fedora, all the services are disabled by default (preset)

Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman socket: Get "http://d/v5.2.5/libpod/_ping": dial unix /run/podman/podman.sock: connect: no such file or directory: unix:///run/podman/podman.sock

[siretart]

is this coming from the Distribution package or is podman installed in some other way?

If this is using the ubuntu 24.04 package, please open a shell and start filing a bug using ubuntu-bug libpod as instructed at https://help.ubuntu.com/community/ReportingBugs