-
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 2.0.5/2.1.1 silently ignores CONTAINER_HOST on centos-8/fedora-32 #8070
Comments
To be clear the problem seems to reproduce on both fedora and centos with latest rpm versions of podman. As There is a slight difference in between 2.1.1 and 2.0.5, the newer one that display the value of the environment variable when using --help, the older one displays the hardcoded default. Still, this has no effect on the bug which applies to both: wrong URL must cause error. |
You need the --remote flag,
Not sure what the Login password is about. |
|
Why do I need to tell it to use remote when I define this variable? This makes impossible to change which backend is used from outside. The other, unnamed, container tool does not require any arguments to use various backends and the environment variable works not only on cli, but also on python module and andible modules, just defining it it tells it to use specific host. Is there another environment variable that needs to be defined to achieve that? It essential to be able to change backend without altering the API calls (or the cli arguments) as this would mean: alter the code that may not be under your control. Another reason for not forcing users to add |
The other unnamed container tool is only remote. It does not have any concept of non-remote operation. Even if the default is localhost, it's always operating on a socket. Podman does not work that way. (Podman-remote does). |
@ssbarnea Using the latest podman, you should be able to provide login credentials via ssh keys and |
Then just install podman-remote and alias podman to podman-remote. There is a field in containers.conf that is not currently exported to allow users to foce the --remote flag to be true, all the time, and then users would have to do podman --remote=false to have local stuff done. I could expose this if people think it would be useful. |
We tell minikube users to use Otherwise the main problem is similar to #4390, to remember to use different programs on different operating systems. One approach would be to not rename "podman-remote" on the other operating systems, but then "podman" is missing. Currently we have OS tabs in the documentation instead, but it does makes it a little more cumbersome to read too: It has tabs for Linux | macOS | Windows, similar to the mess that is for the packages on the "install" page. Right now they have to use "podman1-remote" too (for varlink), but hope to support "podman-remote" in next release*. * See kubernetes/minikube#8596 We ship our own packages for ubuntu, since the official ones were deleted. And refer people to the static release page. https://github.com/containers/podman/releases/tag/v1.9.3
Just built an Doesn't seem to fit in the naming ? |
A friendly reminder that this issue had no activity for 30 days. |
Podman should support this now, and containers.conf has the remote flag that can default local podman to run in remote mode. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Setting
CONTAINER_HOST
should tell podman where to connect to. Setting this variable to a wrong value should make podman return a connection failure and not run with local server. That is very important as it introduces dangerous behaviors where wrong server would be used.Steps to reproduce the issue:
Describe the results you received:
Success listing of running containers from localhost.
Describe the results you expected:
Connection error, something like
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes/No
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: