-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cli: bindings not correctly set in docker #670
Comments
Running an action that bind-mounts folders (e.g. an action using docker-compose) fails. We need to rework the way we configure the bindings a bit differently:
the above supports both (1) actions that need to bind-mount the workspace (or home folder) in another container (by referring to it as For this, we need to figure out a way to specify this using |
Goes back to the way we were binding folders before. issue #670
@ivotron Does this mean that 2 directories Like here
|
yes |
@ivotron Sorry, forgot onething, can you tell me how to reproduce the error ? |
with the change in 40d1abf, we don't experiment errors now. The main issue is that |
@ivotron Thanks |
Goes back to the way we were binding folders before. issue #670
fixes #697 - adds a --runtime flag that allows to provide 'singularity' or 'docker' (default). When singularity is given, the workflow is executed in singularity containers. fixes #670 - correctly configures the bindings for HOME and Github Workflow environment variables fixes #678 - changes the implementation of '--parallel' so that it uses a process pool instead of a thread one.
Goes back to the way we were binding folders before. issue #670
fixes #697 - adds a --runtime flag that allows to provide 'singularity' or 'docker' (default). When singularity is given, the workflow is executed in singularity containers. fixes #670 - correctly configures the bindings for HOME and Github Workflow environment variables fixes #678 - changes the implementation of '--parallel' so that it uses a process pool instead of a thread one.
Goes back to the way we were binding folders before. issue #670
fixes #697 - adds a --runtime flag that allows to provide 'singularity' or 'docker' (default). When singularity is given, the workflow is executed in singularity containers. fixes #670 - correctly configures the bindings for HOME and Github Workflow environment variables fixes #678 - changes the implementation of '--parallel' so that it uses a process pool instead of a thread one.
Goes back to the way we were binding folders before. issue #670
fixes #697 - adds a --runtime flag that allows to provide 'singularity' or 'docker' (default). When singularity is given, the workflow is executed in singularity containers. fixes #670 - correctly configures the bindings for HOME and Github Workflow environment variables fixes #678 - changes the implementation of '--parallel' so that it uses a process pool instead of a thread one.
building an action that uses docker internally results in:
The text was updated successfully, but these errors were encountered: