Marc Villacorta

Perhaps defining a user at volume creation time `-o SshAuthUser=myuser`. And reading that user's `$SSH_AUTH_SOCK` at mount time? Does that make any sense @vieux ?

Changing the `config.json` like this: ```diff diff --git a/config.json b/config.json index e396ffa..9f1009d 100644 --- a/config.json +++ b/config.json @@ -11,6 +11,13 @@ "value" ], "value": "0" + }, + { +...

Related PR: https://github.com/vieux/docker-volume-sshfs/pull/66

+1 for comma-separated lists with autocompletion: `--roles quorum,master,worker`

I can reproduce it like this: ```console $ helm version version.BuildInfo{Version:"v3.10.0", GitCommit:"ce66412a723e4d89555dc67217607c6579ffcb21", GitTreeState:"clean", GoVersion:"go1.19.1"} $ helm create foo Creating foo $ for i in {1..10}; do helm package foo >/dev/null;...

Thanks for doing this @FrenchBen, today I needed this and I ended up here 😄 Maybe putting this feature behind a flag will make it more likely to be accepted...

I like it like this: ``` multipass launch --name master --cpus 2 --mem 2G --disk 4G --cloud-init -

The docker container running the mesos executor not only needs the docker binary but also other host libraries might be needed too such as: ``` --volume /usr/bin/docker:/usr/bin/docker:ro --volume /lib64/libdevmapper.so.1.02:/lib/libdevmapper.so.1.02:ro --volume...

> However, maybe we should think about publishing such an official CLI image like we [used to](https://hub.docker.com/r/argoproj/argocd-cli) @jannfis could you provide some guidance on implementing this? I've briefly reviewed it...

> We can also use argosay image which is something we can manage https://github.com/argoproj/argo-workflows/tree/master/test/e2e/images/argosay/v2 Despite https://github.com/argoproj/argo-workflows/issues/10435, an [argoproj/argosay](https://hub.docker.com/r/argoproj/argosay/tags) `arm64` image has not been published on Docker Hub.