i'm still having issue with the network | Dagger | Page 1

native gyro Jun 10, 2025, 3:46 AM

#

How can I try to reproduce?

wanton adder Jun 10, 2025, 3:47 AM

#

good question

#

i restarted my terminal and now :

! start engine: failed to pull image: failed to run command: exit status 1
│ ✘ starting engine 0.2s
│ ! failed to pull image: failed to run command: exit status 1
│ │ ✘ create 0.2s
│ │ ! failed to pull image: failed to run command: exit status 1
│ │ │ ✔ exec docker ps -a --no-trunc --filter name=^dagger-engine-|^dagger-engine-v0\.18\.9$ --format {{.Names}} 0.1s
│ │ │ ✘ exec docker inspect --type=image registry.dagger.io/engine:v0.18.9 0.0s
│ │ │ ┃ []                                                                                                                                                                     
│ │ │ ┃ Error response from daemon: No such image: registry.dagger.io/engine:v0.18.9                                                                                           
│ │ │ ! failed to run command: exit status 1
│ │ │ ✘ exec docker pull registry.dagger.io/engine:v0.18.9 0.1s
│ │ │ ┃ Error response from daemon: failed to resolve reference "registry.dagger.io/engine:v0.18.9": failed to do request: Head "https://registry.dagger.io/v2/engine/manifests
│ │ │ ┃ ": rejecting registry.dagger.io:443 because traffic from evaluating PAC file: getting PAC interpreter: Get "http://wpad/wpad.dat": dial tcp: lookup wpad: no such host 
│ │ │ ! failed to run command: exit status 1```

native gyro Jun 10, 2025, 3:47 AM

#

$ git ls-remote --symref https://github.com/kpenfound/dagger-modules HEAD HEAD^{}
ref: refs/heads/main    HEAD
f7964245d0146dd3810f247c6c09eb33518d4654    HEAD

wanton adder Jun 10, 2025, 3:48 AM

#

ref: refs/heads/main    HEAD
f7964245d0146dd3810f247c6c09eb33518d4654        HEAD```

#

same

native gyro Jun 10, 2025, 3:52 AM

#

Can you try
https://www.ssllabs.com/ssltest/analyze.html?viaform=on&d=github.com/kpenfound/dagger-modules

https://www.ssllabs.com/ssltest/analyze.html?viaform=on&d=registry.dagger.io

#

I see

#

hanging

#

Now I see

#

maybe it was just calculating the report. 👍 yeah, top one took twice as long, all healthy

#

===
tried 👍

docker pull registry.dagger.io/engine:v0.18.9
v0.18.9: Pulling from engine
Digest: sha256:ec870f3eae2d40e7393bc2ee1a004fbc148cdf7328f116dc7cc51305433007ea
Status: Image is up to date for registry.dagger.io/engine:v0.18.9
registry.dagger.io/engine:v0.18.9

#

@wanton adder looks like it's your proxy, likely...

│ │ │ ┃ ": rejecting registry.dagger.io:443 because traffic from evaluating PAC file: getting PAC interpreter: Get "http://wpad/wpad.dat": dial tcp: lookup wpad: no such host 
│ │ │ ! failed to run command: exit status 1

#

an AI analysis

That error is related to PAC (Proxy Auto-Config) and specifically a failed attempt to download and use a wpad.dat file to determine proxy settings.

What’s Happening?
Your system (or a library in your application, likely Docker or a Go program using the system's proxy settings) is trying to evaluate a PAC file to decide whether or not to use a proxy for the request to https://registry.dagger.io.

PAC files are JavaScript files (usually called wpad.dat) used to define logic like:

javascript
Copy
Edit
function FindProxyForURL(url, host) {
  if (dnsDomainIs(host, ".internal.company.com")) {
    return "DIRECT";
  }
  return "PROXY proxy.example.com:8080";
}
The error message:

yaml
Copy
Edit
rejecting registry.dagger.io:443 because traffic from evaluating PAC file: getting PAC interpreter: Get "http://wpad/wpad.dat": dial tcp: lookup wpad: no such host

means:

Your system is configured to auto-detect proxy settings.

It's trying to retrieve the PAC file via WPAD (Web Proxy Auto-Discovery Protocol) at http://wpad/wpad.dat.

The DNS lookup for wpad (which should resolve to something like wpad.mycompany.local) failed.

Because the PAC file could not be retrieved, the program chooses to reject the request to registry.dagger.io.

wanton adder Jun 10, 2025, 4:07 AM

#

weird

native gyro Jun 10, 2025, 4:09 AM

#

makes me wonder where in your environment that exists
maybe in shell...
env | grep -i proxy

or maybe at another layer

wanton adder Jun 10, 2025, 4:10 AM

#

nothing here env | grep -i proxy

#

here yes : scutil --proxy
<dictionary> {
ExceptionsList : <array> {
0 : *.local
1 : 169.254/16
}
FTPPassive : 1
ProxyAutoConfigEnable : 1
ProxyAutoConfigURLString : http://wpad/wpad.dat
ProxyAutoDiscoveryEnable : 1
}

native gyro Jun 10, 2025, 4:13 AM

#

hearing suggestion to turn off MacOS Auto Proxy Discovery, Automatic Proxy Configuration under System Settings → Network

More AI

confirms that your macOS system proxy settings are trying to auto-discover proxy settings via WPAD (ProxyAutoDiscoveryEnable = 1) and are also manually pointing to http://wpad/wpad.dat (ProxyAutoConfigEnable = 1).

Here's what's going wrong:
The system is trying to fetch a PAC file at http://wpad/wpad.dat.

But the domain wpad doesn’t resolve (no DNS entry), so the request fails.

Some Go programs, Docker, or other tools that rely on macOS’s proxy settings try to evaluate that PAC file and fail — which then blocks the request (as you're seeing with registry.dagger.io).

#

curl -k http://wpad/wpad.dat
curl: (6) Could not resolve host: wpad

#

wanton adder Jun 10, 2025, 1:11 PM

#

fixed thx

#i'm still having issue with the network