Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Karen-Schoener opened this issue May 10, 2024 · 0 comments · May be fixed by #1479
Open

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

Karen-Schoener opened this issue May 10, 2024 · 0 comments · May be fixed by #1479

Comments

@Karen-Schoener
Copy link
Collaborator

Karen-Schoener commented May 10, 2024

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.

@Karen-Schoener Karen-Schoener linked a pull request May 16, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant