Skip to content

CLI: skupper init: improve recommendation if podman endpoint is not available #1471

@Karen-Schoener

Description

@Karen-Schoener

Describe the bug

As root, run:

# systemctl stop podman.socket
# skupper --platform podman init

Note that the recommendation in the CLI output assumes non-root user.

# ./skupper --platform podman init
Podman endpoint is not available: unix:///run/podman/podman.sock

Recommendation:

        Make sure you have an active podman endpoint available.
        On most systems you can execute:

                systemctl --user enable --now podman.socket

        Alternatively you could also create your own service that runs:

                podman system service --time=0 <URI>

        You can get concrete examples through:

                podman help system service

I assume that the Recommendation should check the uid.

If root user runs "# skupper --platform podman init", I assume that this line in the output should change from this:

                systemctl --user enable --now podman.socket

to this:

                systemctl  enable --now podman.socket

Environment details
Observed in skupper client version: 1.6.0.

Metadata

Metadata

Assignees

No one assigned

    Labels

    cliIssues associated with the CLIv1issue for v1 skupper version

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions