Problems running rkt fly on CoreOS #2160
Comments
As a workaround you could use @marineam, @steveeJ: Not sure who is doing rkt packaging for CoreOS, but if you are installing stage1 images to {
"rktKind": "paths",
"rktVersion": "v1",
"stage1-images": "/usr/share/rkt"
} Please see https://github.com/coreos/rkt/blob/master/Documentation/configuration.md#rktkind-paths for details. |
@krnowak ok, I suspect this came about simply because the ebuild larely dates to when there was only one stage1 image and the change to shipping multiple stage1s didn't really catch anyones attention :( We'll get it fixed this week |
This fix will be rolling out in alpha 955.0.0 |
Using the latest CoreOS from today (949 that includes rkt 1.0), I thought I'd give rkt fly a tryout.
1st issue - it seems
rkt
andCoreOS
have different ideas about where stage-1 images should live.On CoreOS the file is actually here
/usr/share/rkt/stage1-fly.aci
I tried
--stage1-name
but that didn't work (since the stage1 isn't preloaded into the store). The docs hinted that I might be able to do--stage1-name=coreos.com/rkt/stage1-fly
, but it can'tThe text was updated successfully, but these errors were encountered: