I worked out the command to run after reboot is: /usr/local/bin/kubelet --manifest-url=http://metadata.google.internal/computeMetadata/v1/instance/attributes/google-container-manifest --manifest-url-header=Metadata-Flavor:Google --config=/etc/kubernetes/manifests
seems like a bug that it's not run automatically. not sure where to report this though. On Thursday, July 14, 2016 at 2:51:42 PM UTC+1, henry w wrote: > > hi. I have a google compute instance which is meant to run a container, > configured via metadata. > > It was created like so: > > gcloud deployment-manager deployments create…` command, passing in a file > which contains a spec like > > ```- name: xxx > type: compute.v1.instance > properties: > metadata: > items: > - key: google-container-manifest > value: | > apiVersion: v1 > kind: Pod``` > > this all starts fine. the problem is rebooting that, the pod does not > start automatically. I can see in the console that all the metadata is > still attached to the instance, but kubelet has not started i guess and > there are no docker processes. > > anyone know how to restart so it runs kube processes automatically? thanks > > fyi I rebooted with `sudo reboot` as described here > https://cloud.google.com/compute/docs/instances/restarting-an-instance > -- You received this message because you are subscribed to the Google Groups "Containers at Google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-containers. For more options, visit https://groups.google.com/d/optout.
