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

proxy settings are not applied when using podman machine init --now while it is using init and then start #14640

Closed
benoitf opened this issue Jun 17, 2022 · 5 comments · Fixed by #14665
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. machine

Comments

@benoitf
Copy link
Contributor

benoitf commented Jun 17, 2022

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

Instead of doing podman machine init and then podman machine start, do podman machine init --now
Steps to reproduce the issue:

  1. edit containers.conf file and add http_proxy/https_proxy env variables
[containers]

[engine]
  env = ["https_proxy=http://10.0.0.123:9090", "http_proxy=http://10.0.0.123:9090"]
  1. do podman machine init --now

  2. then connect to ssh to the machine

$ podman machine ssh
  1. check environment variables
 env | grep http

there is nothing !

  1. now, instead of doing podman machine init --now, do that in two steps

podman machine init and then podman machine start

connect to the ssh machine:
podman machine ssh

and check env

 env | grep http
https_proxy=http://10.0.0.123:9090
http_proxy=http://10.0.0.123:9090

env variables are set

Describe the results you received:
proxy settings are not set

Describe the results you expected:
proxy settings are set

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

(paste your output here)

Output of podman info --debug:

(paste your output here)

Package info (e.g. output of rpm -q podman or apt list podman):

(paste your output here)

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)

Yes/No

Additional environment details (AWS, VirtualBox, physical, etc.):

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Jun 17, 2022
@rhatdan
Copy link
Member

rhatdan commented Jun 17, 2022

@ashley-cui @baude PTAL

@Luap99 Luap99 added the machine label Jun 17, 2022
@n1hility
Copy link
Member

n1hility commented Jun 18, 2022

FYI issue for proxy support on Windows: #14589

@Luap99
Copy link
Member

Luap99 commented Jun 20, 2022

@benoitf Can you test #14665?

Luap99 added a commit to Luap99/libpod that referenced this issue Jun 20, 2022
podman machine start contains more logic than just the simple vm.Start()
call. Instead of duplicating this into inti we just call start().

[NO NEW TESTS NEEDED] I have no way to test this right now.

Fixes containers#14640

Signed-off-by: Paul Holzinger <[email protected]>
@baude
Copy link
Member

baude commented Jun 21, 2022

@benoitf anything to report?

@benoitf
Copy link
Contributor Author

benoitf commented Jun 21, 2022

@baude I replied on the PR that it was working #14665 (comment)

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 20, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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. machine
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants