Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rocket needs the stage1.aci file in the same location as the rkt binary #5

Merged
merged 3 commits into from
Feb 20, 2015
Merged

Rocket needs the stage1.aci file in the same location as the rkt binary #5

merged 3 commits into from
Feb 20, 2015

Conversation

rasschaert
Copy link
Contributor

@yuvadm
Copy link
Owner

yuvadm commented Feb 11, 2015

@rasschaert Interesting bug! However, I don't believe putting stage1.aci in /usr/bin is a solution that should be done on the package level. If I understand correctly you can specific the location for this file? In that case, that should be the workaround, and not polluting /usr/bin.

If I didn't understand the nature of the bug, I'm open to being convinced otherwise.

@yuvadm
Copy link
Owner

yuvadm commented Feb 11, 2015

And actually, @jonboulle mentioned the exact fix here rkt/rkt#457 (comment)

If you go ahead and implement that, I'll gladly merge the fix :)

@rasschaert
Copy link
Contributor Author

As far as I can tell the the code that tells rkt where stage1.aci is can't be changed with a build option. It assumes stage1.aci is in the same directory as the rkt binary unless the --stage1-image option is given on the command line.

Do you reckon I should open an issue upstream to add that option to the build script?

@yuvadm
Copy link
Owner

yuvadm commented Feb 12, 2015

@rasschaert absolutely, this is a blocking upstream fix.

@rasschaert
Copy link
Contributor Author

Filed at rkt/rkt#520

@yuvadm
Copy link
Owner

yuvadm commented Feb 12, 2015

@rasschaert
Copy link
Contributor Author

They added the option to specify your own stage1 file at runtime:

rkt run --stage1-image=/path/to/stage1.aci example.com/app

Without that option rkt just dies with:

Error finding stage1 image "/usr/bin/stage1.aci": rkt only supports http or https URLs (/usr/bin/stage1.aci)

There doesn't appear to be a build option to change the default location where rkt looks for the stage1 file.

@jonboulle
Copy link

Sorry about that guys - just fixed upstream. You'll just need to set RKT_STAGE1_IMAGE to the appropriate location (for where you will actually write stage1.aci to disk) when running the build script. Let us know if you have any other problems!

@jonboulle
Copy link

(also to be clear; this is on master now, and will make it into the next tagged release, probably next week)

@yuvadm
Copy link
Owner

yuvadm commented Feb 13, 2015

@jonboulle thanks for the quick fix! @rasschaert would you like to update the patch so we have it ready for the release?

@rasschaert
Copy link
Contributor Author

Been looking into it. The source archive doesn't seem like a good base to build on because of rkt/rkt#522.

Probably best to wait until that gets resolved or to go forward using a git clone and check out the correct tag.

@yuvadm
Copy link
Owner

yuvadm commented Feb 13, 2015

There's rocket-git which isn't maintained by me, you can try to ping the maintainer about it.

@rasschaert
Copy link
Contributor Author

It'd be nice to have a reproducible package for the tagged releases, like what you had before.

When building from the source .tar.gz or a git tag, you can even support other architectures. 😃

@rasschaert
Copy link
Contributor Author

Updated the PKGBUILD for rocket again so that it builds from the source archive and sets RKT_STAGE1_IMAGE to /usr/lib/rkt/stage1.aci.

Also took the liberty of adding myself as a contributor at the top of the file.

@yuvadm
Copy link
Owner

yuvadm commented Feb 19, 2015

@rasschaert looks great, will test and merge soon :) Thanks!

yuvadm added a commit that referenced this pull request Feb 20, 2015
Rocket needs the stage1.aci file in the same location as the rkt binary
@yuvadm yuvadm merged commit 7c107cc into yuvadm:master Feb 20, 2015
@rasschaert
Copy link
Contributor Author

I should probably have bumped pkgrel to 2, since you had already put out a PKGBUILD on AUR for v0.3.2. Want another PR for that or will you just edit that in yourself?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants