[Feature Request] QNAP Docker support about xpipe

[crschnick]

Hmm, the only thing xpipe does to verify whether docker is available is to run docker --help and check the exit code. Maybe something when wrong there? You can try go to Settings -> Troubleshoot -> Launch in debug mode and see exactly what is getting executed and returned.

[hanskokx]

Maybe it's not getting a proper shell first? I'm not sure. Details below.

17:06:48:080 - trace: [proc] Starting command execution ... {
    baseCommand=docker --help
    shellType=sh
    elevated=false
    workingDirectory=null
}
17:06:48:083 - trace: [proc] Writing line {
    line=echo 'a03b53cf-e4c1-44a2-b39b-0ad2f37d9727';echo '7a0f426d-088b-4d8e-9b7c-c2a3b75af24a' 1>&2;docker --help;echo '85431907-e403-4048-a01f-21744706e609'${?}END;echo '0dfd651f-6b20-42a6-93d3-a87802b89765' 1>&2
}
17:06:48:105 - trace: [proc] Stdout finished. Reading exit code ...
17:06:48:105 - trace: [proc] Read: 127END
17:06:48:105 - debug: [proc] Command finished {
    command=docker --help
    finishReason=NORMAL_FINISH
    exitCode=127
}
17:06:48:106 - trace: [proc] Read stdout {
    output=
}
17:06:48:107 - trace: [proc] Stderr finished {
    finishReason=NORMAL_FINISH
}
17:06:48:108 - trace: [proc] Command state switched to finished
17:06:48:109 - trace: [proc] Read stderr {
    output=-sh: line 19: docker: command not found
}

[crschnick]

What is the login shell of your system? Ideally you should connect to that shell type to get all the shell profiles executed

[hanskokx]

/bin/sh, but /usr/bin/zsh is also available.

[crschnick]

Are all the profile files sourced properly when you manually startup a login shell with sh -l?

[crschnick]

For better reproduction, you can try manually connecting with ssh -T user@host because that is what xpipe does internally. The exact command used to connect should also be found somewhere in the debug output

[hanskokx]

It looks like ssh -T gets me to busybox, not a proper shell.

[crschnick]

hmm, any idea why? I don't have QNAP setup to test that. Essentially, xpipe she's the same thing as when you manually open with ssh -T. If you somehow managed to make it start a proper shell, it should work.

[hanskokx]

That's the funny thing. It detects zsh properly and tapping on it will drop me into a zsh shell (but SHELL=/bin/sh still).

[hanskokx]

Aha - if I manually set the PATH variable in the init script for one of the shells, it finds docker.

[crschnick]

Interesting. Honestly these busybox setups are usually not designed for having extensive profile scripts that cover all situations, so I can see why there are some problems like that. If you somehow get it running without explicitly specifying the path, feel free to share.

[hanskokx]

Setting the PATH is a decent enough solution for me 🤷🏻‍♂️

[crschnick]

So I played around a bit with better PATH initialization (hopefully). You can try whether the latest version of https://github.com/xpipe-io/xpipe-ptb work for you without explicitly setting the path