Skip to content
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

[feature] Add custom volumes to local execution using local.DockerRunner #11562

Open
champon1020 opened this issue Jan 28, 2025 · 1 comment
Open

Comments

@champon1020
Copy link
Contributor

Feature Area

/area sdk

What feature would you like to see?

Add a volumes parameter to local.init or local.DockerRunner and mount it when it runs the docker container using DockerTaskHandler.

What is the use case or pain point?

Currently, users cannot mount custom volumes to containers that run pipeline tasks. When local.init is called, the pipeline_root is passed and it is mounted when task containers are running, but it is annoying us in case of mounting multiple directories. Also in my case, I wanted to mount gcloud directory to access to GCP from task containers, but I hesitated to do it because the pipline saves files of task outputs to pipeline_root.

Anyway, I believe allowing us to set custom volumes is probably helpful when executing pipeline in local.

Is there a workaround currently?

Since only pipeline_root is mounted to task containers, you can use it when you want to share files or directories in your local machine.


Love this idea? Give it a 👍.

@champon1020
Copy link
Contributor Author

/assign @champon1020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant