podman --remote does not work #7010
Assignees
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
openshift-ci-robot
added
the
kind/bug
|
I have the same problem with my fedora 32 box with podman v2.0.2. |
|
Here the log-level debug version: |
|
I had the same problem in the Ubuntu packaging. #6598 (comment) Since the packages don't use the https://src.fedoraproject.org/rpms/podman/blob/master/f/podman.spec#_468 https://github.com/containers/podman/blob/v2.0.2/Makefile#L25 REMOTETAGS ?= remote exclude_graphdriver_btrfs btrfs_noversion exclude_graphdriver_devicemapper containers_image_openpgp
bin/podman-remote: .gopathok $(SOURCES) go.mod go.sum $(PODMAN_VARLINK_DEPENDENCIES) ## Build with podman on remote environment
$(GO_BUILD) $(BUILDFLAGS) -gcflags '$(GCFLAGS)' -asmflags '$(ASMFLAGS)' -ldflags '$(LDFLAGS_PODMAN)' -tags "${REMOTETAGS}" -o $@ $(PROJECT)/cmd/podmanSince 911b6d8 (containers/common@6dea667) There is also no verification of this, so this regression just keeps on happening: Most likely it needs to have a test, that podman-remote/podman --remote actually is remote. @lsm5 : Would it be possible to add some kind of regression check to the packaging scripts ? Maybe the packaging issues with ubuntu and fedora should be reported somewhere else... |
|
The thing here is that |
Right, I forgot about that bug. I see the same thing, just that we used |
I can't seem to get $CONTAINER_HOST to work ? |
Looks like you are right. I can reproduce this. |
|
Also the url does not work without adding the default socket path at the end, which is different from how DOCKER_HOST works. It would be nice if you only had to provide |
|
The default setup assumes that you either log in as root, or that you access a user service and a user podman socket. Added some details on how to be able to access the system socket while still logging in as a regular user, here: #6809 |
|
PRs welcome. There is work going on in podman system connection. But we should definitely add some support for DOCKER_HOST. |
jwhonce
added a commit
to jwhonce/podman
that referenced
this issue
Jul 28, 2020
The assumed format for DOCKER_HOST is <schema>://<host>[:<port>][path]. If the ssh schema is used for DOCKER_HOST, "/run/podman/podman.sock" is appended if path is not given. All other schemas are assumed to resolve to a destination running a Podman service as given. usage: `$ DOCKER_HOST=ssh://root@localhost:22 bin/podman ps --all` Issue: containersGH-7010 Signed-off-by: Jhon Honce <jhonce@redhat.com>
jwhonce
added a commit
to jwhonce/podman
that referenced
this issue
Jul 28, 2020
The assumed format for DOCKER_HOST is <schema>://<host>[:<port>][path]. If the ssh schema is used for DOCKER_HOST, "/run/podman/podman.sock" is appended if path is not given. All other schemas are assumed to resolve to a destination running a Podman service as given. usage: `$ DOCKER_HOST=ssh://root@localhost:22 bin/podman ps --all` Issue: containersGH-7010 Signed-off-by: Jhon Honce <jhonce@redhat.com>
jwhonce
added a commit
to jwhonce/podman
that referenced
this issue
Jul 30, 2020
The assumed format for DOCKER_HOST is <schema>://<host>[:<port>][path]. If the ssh schema is used for DOCKER_HOST, "/run/podman/podman.sock" is appended if path is not given. All other schemas are assumed to resolve to a destination running a Podman service as given. usage: `$ DOCKER_HOST=ssh://root@localhost:22 bin/podman ps --all` Issue: containersGH-7010 Signed-off-by: Jhon Honce <jhonce@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Sep 12, 2020
The assumed format for DOCKER_HOST is <schema>://<host>[:<port>][path]. If the ssh schema is used for DOCKER_HOST, "/run/podman/podman.sock" is appended if path is not given. All other schemas are assumed to resolve to a destination running a Podman service as given. usage: `$ DOCKER_HOST=ssh://root@localhost:22 bin/podman ps --all` Issue: containersGH-7010 Signed-off-by: Jhon Honce <jhonce@redhat.com> Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Sep 12, 2020
Issue: containersGH-7010 Signed-off-by: Jhon Honce <jhonce@redhat.com> Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan
added a commit
to rhatdan/podman
that referenced
this issue
Sep 14, 2020
Issue: containersGH-7010 Signed-off-by: Jhon Honce <jhonce@redhat.com> Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
podman --remotedoes not work.It looks like the options
--remoteand--urlare simply ignored.podman-remoteworksSteps to reproduce the issue:
podman --remote --url "abcd" ps -aDescribe the results you received:
list of local containers
Describe the results you expected:
list of remote containers or an error if the service is not running or the url was invalid
e.g.
Error: Get "http://d/v1.0.0/libpod../../../_ping": dial unix ///run/podman/podman.sock: connect: no such file or directoryAdditional information you deem important (e.g. issue happens only occasionally):
Output of
podman version:Output of
podman info --debug:Additional environment details (AWS, VirtualBox, physical, etc.):
physical
The text was updated successfully, but these errors were encountered: