-
-
Notifications
You must be signed in to change notification settings - Fork 281
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
Add multi-arch support #245
Comments
I am definitely interested in ARM, no doubt. I don't know how much the other platforms are used, but I'm not necessarily against them. I'll have to look into that more unless you can chime in and fill me in, can those be built on Travis-CI still or do they have to be built in parity? |
It seems that the instructions I've referenced use Docker Hub to build the images, I'll fork your repo and see if I can add the manifest list without changing your Travis scripts. |
It's going to be more complicated than that I'm afraid. From what I see, since this jekyll image and its variants are being build from Travis (a x86 machine) and the result will always be a x86 image. To build for ARM and other architectures we need the host machine to be from that architecture (since the base-image to be used has to be from that arch. as well). The solution on x86-only hosts is to inject the |
Hi ! Setting up multi-arch Docker support on a single host is a pain in the ass with Travis CI (Drone.io is easier to use for native builds for example), but I managed to build the Docker version of Jekyll with armv6 support. Blafy/jekyll-docker-arm@f8dd42e Here is a demonstration with a Raspberry Pi first generation (armv6 alias armhf)
I need to clean a few things, try to add the aarch64 (no need for armv7, as it supports v6 binaries) and then I can submit a PR 🙂 @envygeeks How do you want to handle the additionnal images in the repos ? By adding - |
@Blafy tonight I'll set it up so that our images use a configuration tag for the image, so we can split them off into repos with symlinked build files and a configuration that changes the base image each one uses. That way when they get built each one can use it's own base! |
Some news :
|
Closing this since it's a dangling issue, if somebody plans to work with me on this I'll reopen it! |
Request
I think a great addition would be to add support for more architectures than x86_64.
According to here, it would only need to add a manifest list with all the supported architectures and since alpine/ruby already support a few maybe the exact number could be included here?
Examples
armhf, ppc, sparc, etc.
The text was updated successfully, but these errors were encountered: