mounting nfs on google app engine

[pankaj kumar]

I am trying to mount a nfs share onto a app engine container. Everything seems to work other than the fact that the container has a 172.* ip address and the default network is a 10.* ip address. Is there a way to set networking in the containers to get the same 10.* ip address? (Bridged vs nat or something?)

[pankaj kumar]

Docker has this --net=host parameter which will enable host networking. The container gets ip address same as the host. Can we have that in the google app engine? That way services like nfs on the same network that need to connect to the client can be utilized in the container. 

[pankaj kumar]

It seems aws does not support it either: https://webcache.googleusercontent.com/search?q=cache:9c6QEoKcS3gJ:https://forums.aws.amazon.com/thread.jspa%3FthreadID%3D177850+&cd=1&hl=en&ct=clnk&gl=us

Is it possible to change some code somewhere in the sdk to enable --net=host? Or is it possible to access the host machine in a clean way to run some commands and create a virtual ethernet adapter and link it to the docker instance?

Thanks

[Adam (Cloud Platform Support)]

The container networking behavior can't be modified by the SDK. This is managed by the backend when the host VM is provisioned. It may be technically possible to SSH into the host VM in user-managed mode, but this would need to be done manually each time a new VM instance is spun up and would not be practical. You would be much better off using a standard Compute Engine instance where you can tailor Docker to your specific needs.

It's not likely that this would be supported on App Engine Flex, as it can cause problems like allowing the container to reboot the host VM, and is also not supported in Container Engine due to it being considered an anti-pattern, among other things. With that being said, you are free to open a feature request for this on the issue tracker.