Skip to content

http_proxy et.al. not set in a new VM until restart #365

Closed
@thopoi

Description

@thopoi

Version 0.7.2

http_proxy, https_proxy, ftp_proxy, and no_proxy are not set in new VM until the VM is stopped and restarted.
This seems to be a small regression from 0.7.1.

Steps to reproduce.

export http_proxy=http://myproxy:12345
limactl stop 
limactl delete default
limactl start </dev/null   # new vm with defaults
lima bash -c '[[ -z "$http_proxy" ]] && echo http_proxy UNSET || echo http_proxy OK'
  ==> http_proxy UNSET
limactl stop
limactl start
lima bash -c '[[ -z "$http_proxy" ]] && echo http_proxy UNSET || echo http_proxy OK'
  ==> http_proxy OK

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions