You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The drive letter has been specified
-v /:/mnt/host:ro
Network speed can only monitor one's own network card
When I try to use the variable DASHDOT-USE-NEWORK-INTERFACE
Start failed
How to reproduce
No response
Relevant log output
yarn run v1.22.19
$ node .
listening on *:3001
Error: Command failed: mountpoint -q /internal_mnt/host_sys || nsenter --net=/mnt/host/proc/1/ns/net mount -t sysfs nodevice /internal_mnt/host_sys
nsenter: cannot open /mnt/host/proc/1/ns/net: No such file or directory
at ChildProcess.exithandler (node:child_process:422:12)
at ChildProcess.emit (node:events:517:28)
at maybeClose (node:internal/child_process:1098:16)
at Socket.<anonymous> (node:internal/child_process:450:11)
at Socket.emit (node:events:517:28)
at Pipe.<anonymous> (node:net:350:12) {
code: 1,
killed: false,
signal: null,
cmd: 'mountpoint -q /internal_mnt/host_sys || nsenter --net=/mnt/host/proc/1/ns/net mount -t sysfs nodevice /internal_mnt/host_sys',
stdout: '',
stderr: 'nsenter: cannot open /mnt/host/proc/1/ns/net: No such file or directory\n'
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Info output of dashdot cli
No response
What browsers are you seeing the problem on?
No response
Where is your instance running?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Description of the bug
Tag:mauricenino/dashdot:sha-2356692
The drive letter has been specified
-v /:/mnt/host:ro
Network speed can only monitor one's own network card
When I try to use the variable DASHDOT-USE-NEWORK-INTERFACE
Start failed
How to reproduce
No response
Relevant log output
Info output of dashdot cli
No response
What browsers are you seeing the problem on?
No response
Where is your instance running?
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: