dat doctor crashes when running inside docker container about dat

[okdistribute]

Can you try in the latest dat with ndoe 12? We are also no longer supporting dat-doctor.

[mkroehnert]

Hi @okdistribute I will try with the lates version and report the result here.

One additional note, I was not using dat-doctor package but dat doctor that is built into the dat cli.

[mkroehnert]

@okdistribute here are the compilation result, when switching to the node:12-alpine Docker image:

https://gitlab.com/mkroehnert/dat-doctor-docker/snippets/1958240

Basically, the utp-native module fails to compile.

When I run dat doctor in the generated image, I still get a segmentation fault in the basic test.

Basic Test:

/ $ dat doctor
Welcome to Dat Doctor!

Software Info:
  linux x64
  Node v12.16.1
  Dat Doctor v2.1.2
  dat v13.13.1

Running Basic Tests (Checks your Dat installation and network setup)

✖ Who am I?
    ERROR: Could not detect public ip / port
✔ Loaded native modules
✔ Resolved Dat Doctor Server
✔ Successful data transfer with Dat Doctor via TCP
⠙ Connecting to Dat Doctor, 45.55.78.106:8887Segmentation fault (core dump

The Peer-to-Peer test seems to run:

/ $ dat doctor
Welcome to Dat Doctor!

Software Info:
  linux x64
  Node v12.16.1
  Dat Doctor v2.1.2
  dat v13.13.1

To start a new Peer-to-Peer test, press ENTER.
Otherwise enter test ID.
>
✖ Who am I?
    ERROR: Could not detect public ip / port
✔ Loaded native modules

Running a new Peer-to-Peer test

To check connectivity with another computer, run the command:

  dat doctor 1580ff674295b824fd80ebf7f1dd57358646a0ed716d77913de43637e28a6698

Trying to Connect:
  46.5.5.180:3282

[mkroehnert]

Just realized what was meant with dat doctor is no longer supported.

I installed dat@next, where this command was removed.
Since I solved the sync issue that I wanted to test with this image, this issue can stay closed.

[okdistribute]

thank you!