LSF should support output/error file path that exists only in a container

As of now LSF cannot handle a scenario where the output/error file path exists only in the container and does not exist on the underlying host where the container is running .
For example:
bsub -o <path_in_container_only> --app <my_bapp> <script>

In the above case, we use the LSF application <my_bapp> to run a job in a container.
We would like to send the output of <script> to <path_in_container_only> for the
scenario where <path_in_container_only> is a valid path in container, not on host.
<path_in_container_only> container path is a NFS path inside container not available on the underlying host.

In the above scenario, output is not written in the path <path_in_container_only> after the job is run.

We would like IBM to consider supporting this feature given the increasing use of LSF in a container based environment.

Needed By

Quarter

Post comment

Admin

Bill McMillan

Reply
| Mar 8, 2023

LSF is treating the whole container as "the job". Nothing from LSF is running "in" the container. SBD/RES are capturing the stdout/err from the container, which cannot be written to a path that only exists in the container.

Copying the output from the host, into the container and then to the nfs mount would be fairly inefficient.

The simplest solution would be to just have the script write directly to the path:
"bsub -app script > /path_in_container"

0 reply Hide replies

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Please enter your email address

RELATED IDEAS

LSF should support output/error file path that exists only in a container