Existing Resources
- [ x] Please search the existing issues for related problems
- [ x] Consult the product documentation : Docs
- [ x] Consult the FAQ : FAQ
- [ x] Consult the Troubleshooting Guide : Guide
- [ x] Reviewed existing training videos: Youtube
Describe the bug
When adding a process that starts in the background (via the & directive) to custom_startup.sh, the docker image will repeatedly complain that it can't find a process via the kill command.
To Reproduce
Steps to reproduce the behavior:
- create a
dockerfile that adds a custom_startup.sh file
- add a background process that starts with the
& directive
- Check logs
Expected behavior
No error message
Screenshots

Workspaces Version
Version 1.12
Workspaces Installation Method
Standalone workspaces docker image
Client Browser (please complete the following information):
N/A
Workspace Server Information (please provide the output of the following commands):
Fedora 37 Docker Host
Additional context
Does not happen if not starting in background (however this in turn is blocking the watchdog loop that follows custom_startup.sh)
Existing Resources
Describe the bug
When adding a process that starts in the background (via the
&directive) tocustom_startup.sh, the docker image will repeatedly complain that it can't find a process via thekillcommand.To Reproduce
Steps to reproduce the behavior:
dockerfilethat adds acustom_startup.shfile&directiveExpected behavior
No error message
Screenshots

Workspaces Version
Version 1.12
Workspaces Installation Method
Standalone workspaces docker image
Client Browser (please complete the following information):
N/A
Workspace Server Information (please provide the output of the following commands):
Fedora 37 Docker Host
Additional context
Does not happen if not starting in background (however this in turn is blocking the watchdog loop that follows
custom_startup.sh)