-
Notifications
You must be signed in to change notification settings - Fork 887
stage1-images directory doesn't contain asc files for the aci images #3320
Comments
@kfirufk thanks for the issue report. Can you do a |
sure.. it happens on calico-node and kubelet. calico-node:
kubelet
|
@kfirufk thank you a lot for providing the systemd unit files, that helped a lot for debugging.
Nevertheless, I am trying to understand what you are trying to accomplish. |
Hi! thanks a lot for your response. I misunderstood the rkt documentation which led me to believe that I must add this configuration for rkt to find the stage1-images. removing the file /etc/rkt/paths.d/paths.json and restarting the service did the trick. thanks again! |
Environment
rkt Version: 1.14.0
appc Version: 0.8.7
Go Version: go1.7.1
Go OS/Arch: linux/amd64
Features: -TPM +SDJOURNAL
Linux 4.7.3-coreos-r2 x86_64
NAME=CoreOS
ID=coreos
VERSION=1185.2.0
VERSION_ID=1185.2.0
BUILD_ID=2016-10-20-2326
PRETTY_NAME="CoreOS 1185.2.0 (MoreOS)"
ANSI_COLOR="1;32"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://github.com/coreos/bugs/issues"
systemd 231
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS -ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN
What did you do?
configured rkt paths to overcome some deprecated configuration in kubernetes by creating
the file "/etc/rkt/paths.d/paths.json" with the content:
{
"rktKind": "paths",
"rktVersion": "v1",
"stage1-images": "/usr/lib/rkt/stage1-images"
}
What did you expect to see?
when starting rkt containers, they should start properly.
What did you see instead?
Oct 26 14:21:57 coreos-2.tux-in.com kubelet-wrapper[22576]: image: using image from file /usr/lib/rkt/stage1-images/stage1-fly.aci
Oct 26 14:21:57 coreos-2.tux-in.com kubelet-wrapper[22576]: run: open /usr/lib/rkt/stage1-images/stage1-fly.aci.asc: no such file or directory
so it tires to find an asc file and it's not there.
should I manually sign the aci or am I missing something ?
The text was updated successfully, but these errors were encountered: