lima-vm / lima-vm/lima

[WSL2] cidata scripts incorrectly set proxy variables

Open
#3,268 1 comment 0 reactions 0 assignees View on GitHub
host/Windows
Dominant language
Go
Stars
21.9k
Forks
957
Avg merge
2d 6h
Merged PRs (30d)
53

Description

### Description

When proxy is set to localhost like
```bat
set ftp_proxy=http://localhost:2121
```

During machine creation this will be replaced with a predefined SlirpGateway, which is not a thing for WSL2 template

```sh
[lima@ ~]$ ip route
default via 172.31.176.1 dev eth0 proto kernel
172.31.176.0/20 dev eth0 proto kernel scope link src 172.31.181.242
[lima@ ~]$ env | grep -i proxy
ftp_proxy=http://192.168.5.2:2121
FTP_PROXY=http://192.168.5.2:2121
```

This is probably result in some programs failing to work and also breaks integration test.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.