This repository was archived by the owner on Feb 24, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 24, 2020. It is now read-only.
error setting up stage0 #2180
Description
I started a container and then killed it (SIGINT) while rkt was still loading it from the CAS. When I went to run it again, it failed to run, complaining run: error setting up stage0: open ...: no such file or directory.
core@apollo ~ $ rkt version
rkt Version: 1.0.0
appc Version: 0.7.4
Go Version: go1.4.3
Go OS/Arch: linux/amd64
Features: -TPM
$ rkt list
UUID APP IMAGE NAME STATE CREATED STARTED NETWORKS
core@apollo ~ $ rkt image list
ID NAME IMPORT TIME LAST USED SIZE LATEST
sha512-0472a487bcbd coreos.com/rkt/stage1-coreos:1.0.0 4 days ago 4 days ago 134MiB false
sha512-ee20d692cda7 strongswan 4 days ago 4 days ago 565MiB false
core@apollo ~ $ sudo rkt run strongswan --interactive
image: using image from local store for image name coreos.com/rkt/stage1-coreos:1.0.0
image: using image from local store for image name strongswan
^C
Woops, I forgot to override the exec flag.
core@apollo ~ $ sudo rkt run strongswan --interactive --exec /bin/bash
image: using image from local store for image name coreos.com/rkt/stage1-coreos:1.0.0
image: using image from local store for image name strongswan
run: error setting up stage0: open /var/lib/rkt/cas/tree/deps-sha512-8f4a912ea544495e0d920bbef506fac877ac0c9d22416373993485d5ad935fe6/image: no such file or directory
Here is what that directory looks like:
apollo ~ # ls /var/lib/rkt/cas/tree/deps-sha512-8f4a912ea544495e0d920bbef506fac877ac0c9d22416373993485d5ad935fe6
manifest rootfs
The manifest looks good:
apollo ~ # cat /var/lib/rkt/cas/tree/deps-sha512-8f4a912ea544495e0d920bbef506fac877ac0c9d22416373993485d5ad935fe6/manifest
{"acKind":"ImageManifest","acVersion":"0.7.1+git","name":"strongswan","labels":[{"name":"arch","value":"amd64"},{"name":"os","value":"linux"}],"app":{"exec":["/usr/sbin/ipsec","start","--nofork","--debug"],"user":"0","group":"0"}}
And the rootfs directory looks fine (I won't include the contents here).
The directory for the stage0 look fine:
apollo ~ # ls /var/lib/rkt/cas/tree/deps-sha512-b42939d872a0645a4dcf08e33b2b99c444f2188225d0bc8290073df498a64b3c/
hash image manifest rendered rootfs
And its manifest:
apollo ~ # cat /var/lib/rkt/cas/tree/deps-sha512-b42939d872a0645a4dcf08e33b2b99c444f2188225d0bc8290073df498a64b3c/manifest
{"acKind":"ImageManifest","acVersion":"0.7.4","name":"coreos.com/rkt/stage1-coreos","labels":[{"name":"version","value":"1.0.0"},{"name":"arch","value":"amd64"},{"name":"os","value":"linux"}],"annotations":[{"name":"coreos.com/rkt/stage1/run","value":"/init"},{"name":"coreos.com/rkt/stage1/enter","value":"/enter"},{"name":"coreos.com/rkt/stage1/gc","value":"/gc"}]}
Activity
alban commentedon Feb 16, 2016
I can reproduce the bug more easily by deleting:
Then, I cannot start the image again.
And I also cannot GC the images:
alban commentedon Mar 7, 2016
@iaguis #2242 fixed the "image gc" issue but it didn't fix everything here, did it?
f0 commentedon Mar 17, 2016
@iaguis is there a workaround for this? I am getting this error with rkt 1.1
iaguis commentedon Mar 17, 2016
@f0 After #2258, if you get this error you should be able to re-run the image, the treestore will rebuild itself, and everything should work.
f0 commentedon Mar 17, 2016
@iaguis ok and this will land in 1.2? and when will 1.2 released?
iaguis commentedon Mar 17, 2016
@f0 yes. It wll be released this week.
f0 commentedon Mar 17, 2016
@iaguis ok thank you