René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"dinghy halt \u0026\u0026 dinghy up result in error","articleBody":"Starting \"dinghy up\" the first time works without problem.\r\nIf I stop dinghy by typing \"dinghy halt\" or \"dinghy stop\" the system stopps also without any issues.\r\nBut if I try to restart it again with \"dinghy up\" I always get this error:\r\n```\r\nUnable to verify the Docker daemon is listening: Maximum number of retries (10) exceeded\r\nTraceback (most recent call last):\r\n\t9: from /usr/local/bin/_dinghy_command:12:in `\u003cmain\u003e'\r\n\t8: from /usr/local/Cellar/dinghy/4.6.5/cli/thor/lib/thor/base.rb:440:in `start'\r\n\t7: from /usr/local/Cellar/dinghy/4.6.5/cli/thor/lib/thor.rb:359:in `dispatch'\r\n\t6: from /usr/local/Cellar/dinghy/4.6.5/cli/thor/lib/thor/invocation.rb:126:in `invoke_command'\r\n\t5: from /usr/local/Cellar/dinghy/4.6.5/cli/thor/lib/thor/command.rb:27:in `run'\r\n\t4: from /usr/local/Cellar/dinghy/4.6.5/cli/cli.rb:93:in `up'\r\n\t3: from /usr/local/Cellar/dinghy/4.6.5/cli/cli.rb:271:in `start_services'\r\n\t2: from /usr/local/Cellar/dinghy/4.6.5/cli/dinghy/machine.rb:25:in `up'\r\n\t1: from /usr/local/Cellar/dinghy/4.6.5/cli/dinghy/machine.rb:126:in `system'\r\n/usr/local/Cellar/dinghy/4.6.5/cli/dinghy/system.rb:18:in `system': Failure calling `docker-machine start dinghy` (System::Failure)\r\n```\r\nI already tried to use `docker-machine --debug start dinghy` to get more details about the problem, but I do not understand it.\r\n\r\nBefore the upper error is thrown, this message repeats 10 times:\r\n```\r\n(dinghy) Calling .GetSSHHostname\r\n(dinghy) DBG | executing: /usr/local/bin/prlctl list dinghy --output status --no-header\r\n(dinghy) DBG | executing: /usr/local/bin/prlctl list -i dinghy\r\n(dinghy) DBG | Found lease: 10.211.55.32 for MAC: 001C4208D8F8, expiring at 1571651690, leased for 1800 s.\r\n(dinghy) DBG |\r\n(dinghy) DBG | Found IP lease: 10.211.55.32 for MAC address 001C4208D8F8\r\n(dinghy) DBG |\r\n(dinghy) Calling .GetSSHPort\r\n(dinghy) Calling .GetSSHKeyPath\r\n(dinghy) Calling .GetSSHKeyPath\r\n(dinghy) Calling .GetSSHUsername\r\nUsing SSH client type: external\r\nUsing SSH private key: /Users/alex/.docker/machine/machines/dinghy/id_rsa (-rw-------)\r\n\u0026{[-F /dev/null -o ConnectionAttempts=3 -o ConnectTimeout=10 -o ControlMaster=no -o ControlPath=none -o LogLevel=quiet -o PasswordAuthentication=no -o ServerAliveInterval=60 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null docker@10.211.55.32 -o IdentitiesOnly=yes -i /Users/alex/.docker/machine/machines/dinghy/id_rsa -p 22] /usr/local/bin/ssh \u003cnil\u003e}\r\nAbout to run SSH command:\r\nif ! type netstat 1\u003e/dev/null; then ss -tln; else netstat -tln; fi\r\nSSH cmd err, output: \u003cnil\u003e: Active Internet connections (only servers)\r\nProto Recv-Q Send-Q Local Address           Foreign Address         State\r\ntcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN\r\ntcp        0      0 :::22                   :::*                    LISTEN\r\n``` \r\nThe only way to get my development system running again is to destroy the dinghy machine and create a new one. This is really bad, because important datas of my containers gets destroyed as well.\r\n\r\nI use parallels pro 15.1.0 on macOS 10.15 (Catalina)","author":{"url":"https://github.com/mediaessenz","@type":"Person","name":"mediaessenz"},"datePublished":"2019-10-21T09:27:45.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":19},"url":"https://github.com/290/dinghy/issues/290"}