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
What happened?
Following a VSCode example, I found nohup & is not respected.
"postStartCommand": "nohup bash -c 'your-command-here &'" is used as an example of how to start a task in the background. This does not work with devpod. It will run in the foreground. If it is a long-running command, this will block the editor from launching
What did you expect to happen instead?
The command to be run in the background and not block execution.
How can we reproduce the bug? (as minimally and precisely as possible)
Add the following to a devcontainer.json
"postStartCommand": "nohup bash -c 'sleep 60 &'"
Local Environment:
DevPod Version: v0.5.21
Operating System: windows
ARCH of the OS: AMD64
DevPod Provider:
Local/remote provider: docker
Anything else we need to know?
If the output of the command is sent to /dev/null, it works as expected. This could be due to something malformed with the command, but it appears to run the command succesfully. "postStartCommand": "nohup bash -c 'sleep 60 &' >/dev/null 2>&1"
The text was updated successfully, but these errors were encountered:
What happened?
Following a VSCode example, I found
nohup &
is not respected."postStartCommand": "nohup bash -c 'your-command-here &'"
is used as an example of how to start a task in the background. This does not work with devpod. It will run in the foreground. If it is a long-running command, this will block the editor from launchingWhat did you expect to happen instead?
The command to be run in the background and not block execution.
How can we reproduce the bug? (as minimally and precisely as possible)
Add the following to a
devcontainer.json
"postStartCommand": "nohup bash -c 'sleep 60 &'"
Local Environment:
DevPod Provider:
Anything else we need to know?
If the output of the command is sent to
/dev/null
, it works as expected. This could be due to something malformed with the command, but it appears to run the command succesfully."postStartCommand": "nohup bash -c 'sleep 60 &' >/dev/null 2>&1"
The text was updated successfully, but these errors were encountered: