-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
podman system service: what should .Host.RemoteSocket.Path be? #12023
Comments
This looks like a bug. |
@jwhonce could you tackle it? I had a quick look and it seems that the notion of it being a |
A friendly reminder that this issue had no activity for 30 days. |
@jwhonce did you ever get a chance to look at this? |
A friendly reminder that this issue had no activity for 30 days. |
It's being worked on, @github-actions! Like, in the last two hours! #ReadingComprehensionFail #ThankGoodness #WeHaveSomeTimeBeforeTheRobotApocalypse |
A friendly reminder that this issue had no activity for 30 days. |
A friendly reminder that this issue had no activity for 30 days. |
Rather than assuming a filesystem path, the API service URI is recorded in the libpod runtime configuration and then reported as requested. Note: All schemes other than "unix" are hard-coded to report URI exists. Fixes containers#12023 Signed-off-by: Jhon Honce <[email protected]>
A friendly reminder that this issue had no activity for 30 days. |
Rather than assuming a filesystem path, the API service URI is recorded in the libpod runtime configuration and then reported as requested. Note: All schemes other than "unix" are hard-coded to report URI exists. Fixes containers#12023 Signed-off-by: Jhon Honce <[email protected]> Signed-off-by: Daniel J Walsh <[email protected]>
Rather than assuming a filesystem path, the API service URI is recorded in the libpod runtime configuration and then reported as requested. Note: All schemes other than "unix" are hard-coded to report URI exists. Fixes containers#12023 Signed-off-by: Jhon Honce <[email protected]> Signed-off-by: Daniel J Walsh <[email protected]>
Start service with a nonstandard socket:
$ bin/podman system service --timeout=0 tcp:localhost:12345
Run
info
against it:This surprised me. I expected
tcp://<something>:12345
.There is no obvious way to find the socket info:
podman-remote info | grep 12345
returns no output.The text was updated successfully, but these errors were encountered: