-
Notifications
You must be signed in to change notification settings - Fork 40
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
explore migrating to appc #31
Comments
I'll probably play around with appc this week to see if their spec files can be used as a replacement for Dockerfiles. Had a cursory look at the spec and it seems doable. |
Looks like things are finally taking the right direction now: https://coreos.com/blog/oci-image-specification.html Gonna look into OCI instead of appc I guess. |
Had a closer look at OCI and appc/acbuild, I'm not sure it is worth the effort, at least for the near future: pro:
con:
Guess we have to wait a little longer to see how this pans out, once container images become truly interchangeable acbuild looks like a nice alternative. |
would love to see aci support. i started working on it but i am not a bash hacker :-) |
soon(tm) :P
Docker already supports OCI images via runC AFAIK, so OCI seems like the way forward. Also good news from acbuild:
So yea looks like the stars have finally aligned, I might start playing with acbuild soon. :) |
From the appc repo:
That being said Been playing around/thinking about this, current plan:
Should be fairly straight forward judging by some manual test runs with acbuild in a build container, except for the image dependency part. Not a whole lot documentation for that. @mischief How do you usually handle aci images you don't want to publish on quay.io? Is it enough to just serve them via nginx? |
@edannenberg sorry for the late reply - yes, it is enough to simply serve a .aci from a plain webserver, such as: IIRC, it is not necessary but useful to use the ACI discovery metatags like so -
see https://github.com/appc/spec/blob/master/spec/discovery.md for details |
@mischief No worries, time is a very limited resource. ;( Ok, thanks. Sounds easy enough. Looks like OCI support is about to land in |
@edannenberg want to file a seperate issue for that, detailing what problems exist and what parts would get rewritten? |
Perhaps refactor is more fitting. Basically try to make functions pure where possible, less globals, bash naming conventions, tests. That sort of things. Shouldn't affect end users too much if at all. Currently toying with some ideas and argbash. |
Sadly
Ran this manually in a @mischief How do you handle One thing I had totally forgotten in my smooth sailing estimation is multiple dependencies, will need some further modifications in the generic image dependency resolution to support this format:
Shouldn't be too bad, but the rabbit hole goes deeper. Currently when building the Planned new hook in image
|
So apparently Docker can now save OCI bundles when building, which makes acbuild kinda pointless I think, or are there any other advantages? Would just need to add a config option to output OCI bundles which should be fairly trivial. Thoughts? |
Took another look at state of things. img looks kinda interesting though, basically unprivileged |
No more plans for this, OCI output will probably a thing though. |
now that docker also supports appc, acbuild, baci or any of the other appcontainer builders might be a better way of creating containers. Optimally, not having to require docker nor rocket (or systemd, ..) would make it even simpler to play with gentoo, seeing how we can lean on crossdev or just folders for building.
The specification for appcontainers can be found here: https://github.com/appc/spec
The text was updated successfully, but these errors were encountered: