"fusermount": executable not found in $PATH about cloud-sql-proxy

[porridge]

Can you please reconsider this issue? FUSE works fine inside kubernetes pods. You just need to specify:

securityContext:
  privileged: true

in your container spec. We use GCSFuse in a k8s deployment just fine.

It would be great not to have to build one's own cloudsql-proxy image just for this. We have plenty of Cloud SQL instances coming and going, and their list differs between the various GCE projects we run, so -fuse is a perfect fit for us.

[Carrotman42]

The docker image provided does not include support for FUSE. In fact, at least of docker 1.09, FUSE doesn't work through docker anyway. You can specify instances you want to connect to using -instances, or project -projects to have the proxy look for instances in those projects.

[itaigev]

Got it. -instances worked great. Thanks.

On Jul 14, 2016 7:58 PM, "Kevin Malachowski" [email protected]
wrote:

The docker image provided does not include support for FUSE. In fact, at
least of docker 1.09, FUSE doesn't work through docker anyway. You can
specify instances you want to connect to using -instances, or project
-projects to have the proxy look for instances in those projects.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#38 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ACujeNAAq-q3XhS_sCNACQXQnwdkro6Aks5qVmrIgaJpZM4JJi0W
.

[Carrotman42]

Let me know if there's anything else I can do!

[porridge]

So it turns out that while FUSE works on docker and k8s these days, accessing a FUSE filesystem in a neighboring container does not. So -fuse is not currently usable on k8s. But maybe it will be at some point: kubernetes/kubernetes#20698 (comment)