-
Notifications
You must be signed in to change notification settings - Fork 3
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
Feature Request: Images based on other Base OSes #4
Comments
@CpuID yes, I'd love to do this. Here's the problem right now: 1. we build the binaries that we use to build the Docker images in Travis CI; 2. we are limited to the distros that Travis CI has available; and 3. we do this because we were trying to keep the Docker image size small (ie by not including all the stuff needed to build Rubinius). Initially, we got the Rubinius image down to 95mb, but then there were no C/C++ compilers installed and no C-ext gems could be installed. After we added the C/C++ compilers back, the image was back to ~200mb. So maybe this image size isn't a huge problem. Perhaps I could set up a multilevel Docker build (similar to the multilevel Travis CI build I have now), where we first build Rubinius on other base images using a build image, then take the binary from that and build more images that only use the binary. Alternatively, maybe I should just finally set up Concourse CI to build everything. Thoughts? |
@brixen Docker 17.06 (stable) is expected to have the multi-stage build feature, which would allow you to build the binaries in one stage and copy the binaries to a second build stage, leaving the build artifacts from the first stage out of the final image. The new version of Docker should be out sometime this month. |
@derikson I tried using multi-stage build today but I get
Regards, |
To confirm there's an Ubuntu 16.04 Dockerfile in this repo, it has a few issues but it exists at least :) |
Would it be possible to get images built off a couple of other Base OS'es at some point?
Thanks!
The text was updated successfully, but these errors were encountered: