create-with | Easily add common unique identity fields to Laravel models | Database library

Fix build command
go build -o foo

Original build command generate foo directory and output execution file in it.

If you have a public IP, then requests from your instance to the Internet go thru the Internet Gateway. If your instance does not have a public IP then you need to setup Cloud NAT to provide a route to the Internet. This is the simplest solution. If you only need to access Google APIs and services and not the public Internet, see the next option.

Google Cloud NAT

Google also offers Private Google Access to reach only Google APIs and services.

Private Google Access

You should firstly register your function via :func.create:

You can't mount the host's disk to the container (use the same disk in both). You can however mount a directory or another disk. Either way you will be able to store data on it and both OS'es (host & container) will be able to read/write from it.

Let's say you want to store all data in the host OS disk in /datadir/ and you want it to be mounted inside the container under /mnt/disks/data. Below you will find a complete (and tested) example to use:

When you use a command gcloud compute instances create-with-container to create a GCE VM instance running a container image, a Container-Optimized OS (COS) is deployed. This is operating system optimized for running Docker containers. But it lacks many of components you had in a typical Linux distribution.

It has a number of limitations, for instance the COS kernel is locked down; you are unable to install third-party kernel modules or drivers. Containerized applications that depend on kernel modules, drivers and other additional packages that are not available in COS might not work. This is kind of a lockdown environment with a small attack surface, that runs your containers as safe as possible.

For more details please see Container-Optimized OS Overview

It's unlikely that Docker-in-Docker configuration in COS is supported by Google.

Apart from that there are good explanations of why running a nested Docker configuration is troublesome and what a workaround could be:

Is it ok to run docker from inside docker?

Docker in Docker?

Both listed above are based on the original article of the author of the Docker-in-Docker feature Jérôme Petazzoni: Using Docker-in-Docker for your CI or testing environment? Think twice.

I used terraformer to reverse-terraform my compute engine instance instance-container that runs Nginx container.

Here's the result terraform file

I've tried to replicate your issue on my test project and found that:

• persistent disk was created and mounted in read-write mode as expected;

You could docker run your container within startup-script of deeplearningvm.

When you create the VM, you'll need to give it write access to compute so you can delete the instance from within. You should also set container environment variables like gce_zone and gce_project_id at this time. You'll need them to delete the instance.