-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Make --rm flag default for fig run
#943
Comments
👍 (but I would prefer |
It's not the default because that would've been a breaking change. We could make it the default for the next version increment. |
+1 to default |
👍 |
5 similar comments
👍 |
👍 |
+1 |
+1 |
👍 |
+1 !! |
I think defaulting to |
Well this should be, at least, configurable in some way. |
I don't think we're looking to change the default behavior of |
A workaround for docker() {
local args=("$@")
if [[ "$1" = run ]]; then
args=(run --rm "${args[@]:1}")
elif [[ "$1" = container && "$2" = run ]]; then
args=(container run --rm "${args[@]:2}")
fi
command docker "${args[@]}"
} If you don't want the The above is for docker-compose() {
local args=("$@")
if [[ "$1" = run ]]; then
args=(run --rm "${args[@]:1}")
fi
command docker-compose "${args[@]}"
} |
This is nice (albeit quirky) for when you're on linux where bash is the default shell, but cmd.exe doesn't have such facility. |
why --rm is not default for
fig run
? I find containers created by run often useless. Maybe it could be some 'no-rm' flag instead of --rm ?People who I presents fig are confused by this flag.
The text was updated successfully, but these errors were encountered: