search

aj-may / dotdocker

🐳 A utility to help setup a docker development environment with host based routing
MIT License
40 stars 10 forks source link

BUG dotdocker proxy → Cannot read property 'match' of undefined #40

Open maxleistner opened 3 years ago

maxleistner commented 3 years ago 
 ❯ Start dotdocker containers
    ❯ Start proxy
      ↓ Pulling codekitchen/dinghy-http-proxy:latest [skipped]
        → Image already exists
      ✔ Creating dotdocker-proxy
      ✖ Starting dotdocker-proxy
        → Cannot read property 'match' of undefined
    ❯ Start dnsmasq
      ↓ Pulling andyshinn/dnsmasq:latest [skipped]
        → Image already exists
      ✔ Creating dotdocker-dnsmasq
      ⠹ Starting dotdocker-dnsmasq
    Setting up DNS
(node:93501) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'match' of undefined
    at Task.task (/Users/maxleistner/.nvm/versions/node/v14.3.0/lib/node_modules/dotdocker/build/tasks/startContainer.js:27:38)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:93501) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:93501) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

System: macos