Dan Leehr

I commented in [211](https://github.com/rabix/bunny/issues/211#issuecomment-352799232) about this, but I think this issue is where my comment belongs

> We have confirmed that this issue is not specific to the TES backend. Just here to +1 this issue. We've been [exploring rabix bunny among other implementations](https://github.com/Duke-GCB/lando/issues/103) that support...

Originally notified via email, responded with: t looks like the error is coming from here. If you can set a breakpoint and confirm, that would be great: https://github.com/dleehr/DLSFTPClient/blob/533f6c9b6d7380451c9dabeade5b568e537b3bf7/DLSFTPClient/Classes/DLSFTPUploadRequest.m#L276 After the...

Maybe. I'll have to think about it and see if I remember anything useful. I'm also not familiar with the state of other implementations that support kubernetes. But I appreciate...

Tool: https://github.com/common-workflow-language/common-workflow-language/blob/master/v1.0/v1.0/docker-run-cmd.cwl Job: https://github.com/common-workflow-language/common-workflow-language/blob/master/v1.0/v1.0/empty.json

The tool specifies the `bash:4.4.12` container, which has an ENTRYPOINT set: https://github.com/tianon/docker-bash/blob/3682e16bca63b20ab51745afa30156e2740fc5c6/4.4/Dockerfile#L126 When calrissian builds up a container to run, it appears to be providing the command in a way...

According to https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#notes: Docker `Entrypoint` = Kubernetes `command` Docker `Cmd` = Kubernetes `args` We're building both in `KubernetesPodBuilder`: https://github.com/Duke-GCB/calrissian/blob/5cba82c211d3370ffd3c53ba22a5618c56758c67/calrissian/job.py#L205-L206 https://github.com/Duke-GCB/calrissian/blob/5cba82c211d3370ffd3c53ba22a5618c56758c67/calrissian/job.py#L208-L219

At first glance it might seem like we could straighten this out cleanly, but as mentioned in the comments, we need to provide the command as a space-separated string, and...

I tried removing the `command` from the container spec, and pushing `['/bin/sh', '-c']` to the front of args. This stops us from stomping on the entrypoint, and doesn't fail any...

In some cases these arguments map to CWL features (network access), and in some cases they're not achievable on openshift without changing security contexts (--user). I think the first order...