You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proposed Feature:
Introduce a python.docker.volumes configuration option to allow users to specify volumes in the form of mappings, e.g., host_path:container_path. For example:
I will add this option as soon as I'll have time (but can't promise too soon).
Can't suggest a workaround, need time to look deeper (can't right now)
Ideally, there shuld be some extra docker arguments option to be able to specify any additional docker parameters (and workaround situations like this when no direct support available).
I will add this option as soon as I'll have time (but can't promise too soon).
Can't suggest a workaround, need time to look deeper (can't right now)
Ideally, there shuld be some extra docker arguments option to be able to specify any additional docker parameters (and workaround situations like this when no direct support available).
Happy to hear that, can I possibly prepare a PR? Also cant promise too much as I did not develop any plugin so far, but I can give it a try.
You can try - it would be a good exercise in any case. But it will take time to proceed even with PR
(in order to release I need not only to add "volumes" property, but read docker docs first to be sure to cover all potential needs, imagine possible use-cases and write tests to cover them; and ofc. update docs - it all will take time)
Proposed Feature:
Introduce a python.docker.volumes configuration option to allow users to specify volumes in the form of mappings, e.g., host_path:container_path. For example:
python {
docker {
image = "python:3.9"
volumes = ["/path/on/host:/path/in/container", "/another/host/path:/another/container/path"]
}
}
The text was updated successfully, but these errors were encountered: