ImagePull | Pull down the picture to show the rest

Use:

Okay I just found out what the mistake is on my code above. I realized this after looking at example code on pulling image from private registry here: https://docs.docker.com/develop/sdk/examples/#pull-an-image-with-authentication

As it turns out, the RegistryAuth arg in types.ImagePush options expect a base64 encoding string.

So with this code, I can successfully push local image to my private registry.

I think you should use the status channel to get the exit code. The error channel seems to be used to signal if there was an error while talking to the docker daemon, see https://godoc.org/github.com/docker/docker/client#Client.ContainerWait.

This works for me:

Since Garbage Collector is an automated service, there are no kubectl commands or any other commands within GCP to manually trigger Garbage Collector.

In regards to your second inquiry, Garbage Collector is handled by the Master node. The Master node is not accessible to users since it is a managed service. As such, users cannot configure Garbage Collection withing GKE.

The only workaround I can offer is to create a custom cluster from scratch within Google Compute Engine. This would provide you access to the Master node of your cluster so you can have the flexibility of configuring the cluster to your liking.

Edit: If you need to delete old images, I would suggest removing the old images using docker commands. I have attached a github article that provides several different commands that you can run on the node level to remove old images here.

The latest version(v1.11.1) is not pulling. You can try specifying the version like

kubeadm config images pull --kubernetes-version=v1.11.0

@radoslav-stoyanov before use my example do

# docker rmi busybox

then run code

&{0xc0422a65c0 {0 0} false 0x6415a0 0x641540} is not a bad output. This is a perfectly fine struct output. I think the the main problem is here just your lack of golang experience.

I'm a beginner as well and I can imagine that when you see an output like above you thought that "I made a mistake"

No you didn't. It's default fmt behavior when u try to print out a struct which contains pointers.

Checkout this instead of your fmt.Println:

First, the Binds parameter is of the format "source:target[:ro]", so you should have it "/etc/secret.txt:/etc/secret.txt", or "/etc/secret.txt:/etc/secret.txt:ro" if you want it to be read-only.

Second, the format of the data from the reader returned by CopyFromContainer() is a tar archive. Here is a small modification to your code that fixes Binds, and uses tar from the stdlib to extract the bytes from /etc/secret.

In the method ContainerCreate the third parameter is HostConfig that you need to use. If you are interested in setting ports then you should take a look at PortBindings field. Also you need to specify exposed ports for container. You can do this by providing ExposedPorts into container configuration (second parameter).
And I assume that you container will be started in a daemon mode by default because you are using API instead of cli tool.

Here is a working example: