Problem seems to be related to older systemd version. Fixed with beta channel release of coreos.
Am Dienstag, 16. August 2016 15:43:13 UTC+2 schrieb Stefan Vetter: > > Hi all, > > I have problems getting a pod manifest started while everything seems to > work otherwise. > > Attached you can see some log extracts. Please help me here asap as I lost > my apiserver due to this... Sorry to bother you :-( > > sudo /var/lib/rkt/rkt image list > ID NAME SIZE IMPORT TIME LAST USED > sha512-d28b619b92c1 quay.io/coreos/flannel:0.5.5 51MiB 1 hour ago 1 hour > ago > sha512-6358fe5bbaaa quay.io/mulled/curl:latest 38MiB 1 hour ago 1 hour ago > sha512-ac5419bdda2e quay.io/coreos/hyperkube:v1.3.4_coreos.0 852MiB 1 > hour ago 1 hour ago > sha512-eab326aed1be quay.io/coreos/etcd:v3.0.2 83MiB 42 minutes ago 42 > minutes ago > sha512-f6507556ac2f coreos.com/rkt/stage1-coreos:1.7.0 82MiB 16 seconds > ago 16 seconds ago > > sudo /var/lib/rkt/rkt list > UUID APP IMAGE NAME STATE CREATED STARTED NETWORKS > > sudo /var/lib/rkt/rkt version > rkt Version: 1.12.0 > appc Version: 0.8.5 > Go Version: go1.6.2 > Go OS/Arch: linux/amd64 > Features: -TPM +SDJOURNAL > > cat /etc/os-release > NAME=CoreOS > ID=coreos > VERSION=1068.8.0 > VERSION_ID=1068.8.0 > BUILD_ID=2016-07-18-0616 > PRETTY_NAME="CoreOS 1068.8.0 (MoreOS)" > ANSI_COLOR="1;32" > HOME_URL="https://coreos.com/"; > BUG_REPORT_URL="https://github.com/coreos/bugs/issues"; >
