Besides the default way to delay-launch a container, there may be a complex way of running a container, and maybe mounting volumes and pointing to a script might not be the best way
So, hestia may have a --stdin option that will read from STDIN until EOF has been reached, keep it in an executable file and invoke it after sleep time.
It shall not be used with --script nor with the default way, should be exclusive. Args after -- are args for the newly created script
jeffque
commented
1 year ago
Besides the default way to delay-launch a container, there may be a complex way of running a container, and maybe mounting volumes and pointing to a script might not be the best way
So, hestia may have a
--stdinoption that will read from STDIN until EOF has been reached, keep it in an executable file and invoke it after sleep time.It shall not be used with
--scriptnor with the default way, should be exclusive. Args after--are args for the newly created script