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
I have searched the existing issues before opening this feature request.
Describe the feature you would like to see.
It would be super useful if it where possible to modify the arguments passed to Docker when creating a container. Currently I am running into an issue where the /tmp directory is being filled up by a program. I attempted to mount a directory on the host to /tmp but it was overwritten by the default tmpfs /tmp dir.
Describe the solution you'd like.
Somewhere in the wings config a template string or just trimmed down arguments list (from what is actually passed to docker) that can be modified to fit a users needs.
Additional context to this request.
There was also a time when I wanted to change the docker arguments to add the NET_RAW capability to a container but I end up finding a workaround for that.
The text was updated successfully, but these errors were encountered:
The code really doesn't work like this. There isn't a string to template.
We interact with the docker API directly. We aren't executing docker cli commands
Is there an existing feature request for this?
Describe the feature you would like to see.
It would be super useful if it where possible to modify the arguments passed to Docker when creating a container. Currently I am running into an issue where the /tmp directory is being filled up by a program. I attempted to mount a directory on the host to /tmp but it was overwritten by the default tmpfs /tmp dir.
Describe the solution you'd like.
Somewhere in the wings config a template string or just trimmed down arguments list (from what is actually passed to docker) that can be modified to fit a users needs.
Additional context to this request.
There was also a time when I wanted to change the docker arguments to add the NET_RAW capability to a container but I end up finding a workaround for that.
The text was updated successfully, but these errors were encountered: