ddev start install_nvm.sh failed (arch using docker installed from snap)

[visionm45]

So I am trying to spin up a drupal site and I can't get past ddev start. It gives me a

Warning: command 'install_nvm.sh' run as 'jack' failed with exit code 1:
fatal: unable to access 'https://github.com/nvm-sh/nvm.git/': Could not resolve host: github.com
Failed to update nvm with v0.40.3, run 'git fetch' in /home/jack/.nvm yourself. 

running the command in the specified directory changes nothing.

if I try to ignore the fatal error and run ddev composer create drupal/cms anyway I then get a

The following exception probably indicates you are offline or have misconfigured DNS resolver(s)

In CurlDownloader.php line 390:
                                                                                                                       
  curl error 6 while downloading https://repo.packagist.org/packages.json: Could not resolve host: repo.packagist.org  

Any ideas? is this a bug or some crazy networking issue?

btw im on arch linux. I ran docker run --rm -t -p 80:80 -p 443:443 -v "//$PWD:/tmp/projdir" busybox sh -c "echo ---- Project Directory && ls /tmp/projdir" and it gave me a directory listing.

[rfay]

Hi @visionm45 - Your DNS resolution isn't working inside your Docker on arch.

Could not resolve host: github.com

Perhaps you're on a VPN?

If you try docker run -it curlimages/curl -I https://github.com

It also fails, right?

[visionm45]

ah. thank you very much. It was a firewall on my hotspot. I didn't realize it. cheers!

[visionm45]

or well part of it appears to be working
at least new error is being presented.

`Warning: command 'install_nvm.sh' run as 'jack' failed with exit code 124:

Command 'install_nvm.sh' timed out after 30 seconds
If your internet connection is slow, consider increasing the timeout by running this:
`ddev config --default-container-timeout=240 && ddev restart` 
`

[rfay]

I guess your internet is very slow, and you should run the suggested command.

ddev config --default-container-timeout=240 && ddev restart

[visionm45]

does webdb have a lot to download? I do have slow internet. im at timeout 1920 so far. and it's just hanging at Waiting for containers to become ready: [web db]

[rfay]

You can use ddev logs -f (in another window) to watch the build happen. You may have your Docker internet limited even more than your host.

[visionm45]

docker run -it curlimages/curl -I https://github.com seems to work fine now.

mabe I should just try later when I am on a more stable internet?

this is from the ddev logs -f while ddev start is running

+ yarn config set cache-folder /mnt/ddev-global-cache/yarn/classic
/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:22051
    throw new Error(
          ^

Error: Error when performing the request to https://registry.npmjs.org/yarn/latest; for troubleshooting help, see https://github.com/nodejs/corepack#troubleshooting
    at fetch (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:22051:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async fetchAsJson (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:22065:20)
    ... 5 lines matching cause stack trace ...
    at async Object.runMain (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:23648:7) {
  [cause]: TypeError: fetch failed
      at node:internal/deps/undici/undici:13510:13
      at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
      at async fetch (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:22045:16)
      at async fetchAsJson (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:22065:20)
      at async fetchLatestStableVersion (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:21988:20)
      at async fetchLatestStableVersion2 (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:22114:14)
      at async Engine.getDefaultVersion (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:22829:23)
      at async Engine.findProjectSpec (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:22892:40)
      at async Engine.executePackageManagerRequest (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:22952:24)
      at async Object.runMain (/usr/local/lib/node_modules/corepack/dist/lib/corepack.cjs:23648:7) {
    [cause]: ConnectTimeoutError: Connect Timeout Error (attempted addresses: 104.16.3.35:443, 104.16.24.34:443, 104.16.25.34:443, 104.16.31.34:443, 104.16.1.35:443, 104.16.0.35:443, 104.16.2.35:443, 104.16.29.34:443, 104.16.26.34:443, 104.16.30.34:443, 104.16.28.34:443, 104.16.27.34:443, timeout: 10000ms)
        at onConnectTimeout (node:internal/deps/undici/undici:2602:28)
        at Immediate._onImmediate (node:internal/deps/undici/undici:2583:11)
        at process.processImmediate (node:internal/timers:485:21) {
      code: 'UND_ERR_CONNECT_TIMEOUT'
    }
  }
}

Node.js v22.15.0
+ true
+ mkdir -p /home/jack/.yarn/berry
+ ln -sf /mnt/ddev-global-cache/yarn/berry /home/jack/.yarn/berry/cache
+ ln -sf /mnt/ddev-global-cache/nvm_dir/test-web /home/jack/.nvm
+ '[' '!' -f /home/jack/.nvm/nvm.sh ']'
+ log-stderr.sh --timeout 480 install_nvm.sh
=> nvm is already installed in /home/jack/.nvm, trying to update using git
=> fatal: unable to access 'https://github.com/nvm-sh/nvm.git/': Failed to connect to github.com port 443 after 133111 ms: Couldn't connect to server
Failed to update nvm with v0.40.3, run 'git fetch' in /home/jack/.nvm yourself.

[rfay]

We ask people doing issues to give us the output of ddev debug test, you could upload that file here or as a gist at gist.github.com. It would tell us a lot.

However, as you have noted, you seem to have a nonfunctional internet, or nonfunctional internet inside Docker or Docker build.

In addition to giving us the ddev debug test you could try this on a better network, and follow the normal troubleshooting steps like rebooting, temporarily turning off your firewall, etc. https://ddev.readthedocs.io/en/stable/users/usage/troubleshooting/

[visionm45]

here is the output of ddev debug test

ill have to spend some time later checking more of the ddev troubleshooting but I've done the basic stuff already except for trying on a different network.

[rfay]

It looks pretty messed up, in the same way, almost certainly network problems that we can't help you with. Are you running this inside Virtualbox? Or just on a system that has Virtualbox?

I'm pretty sure, as you've diagnosed, that you just have tremendous networking problems, so following the troubleshooting ideas is the right path.

One other thing you can do is ddev poweroff && docker volume rm ddev-global-cache, which will give you a fresh start on the nvm repository (nothing but cache gets deleted)

[stasadev]

It's Manjaro with VirtualBox installed. (I don't think there is anything wrong with it.)

Things I noticed:

• 91% disk space used on /dev/nvme0n1p5 - better to give more space for Docker (probably not related to network problems, but anyway)

• Docker installed with snap found, better to remove that:

  docker client alternate locations:
  /usr/bin/docker
  /bin/docker
  /var/lib/snapd/snap/bin/docker
  

I myself use Manjaro and only install packages from repositories and AUR, never use snap, flatpak because they often have some problems.

[stasadev]

It's odd that http://127.0.0.1 doesn't work inside the container, probably blocked by something. Agreed on network issues.

[rfay]

A classic problem with 127.0.0.1 is using a proxy and not putting that in NO_PROXY, but I don't see proxy settings in your environment, although they might be in your host setup.

[visionm45]

you found the problem. it was because I had docker installed from snap. I also had it install from arch repository. once running it spin up a drupal container quickly. Thanks!