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

Provide z7 archive or WSA installer #14

Closed
woodie opened this issue May 18, 2017 · 7 comments
Closed

Provide z7 archive or WSA installer #14

woodie opened this issue May 18, 2017 · 7 comments

Comments

@woodie
Copy link

woodie commented May 18, 2017

People buillding Docker microsoft/nanoserver images would appreciate a WSA download of the DevKit installer (MSI and EXE are not supported on Nano Server).

https://blogs.technet.microsoft.com/nanoserver/2015/11/18/installing-windows-server-apps-on-nano-server/

See also: https://sourceforge.net/p/p7zip/discussion/383043/thread/87a7a773/

@vassilvk
Copy link
Owner

vassilvk commented May 18, 2017

@woodie - Ruby DevKit is distributed by the good folk behind the RubyInstaller project - I don't plan on distributing it separately from them.

I can suggest the following:

Since Ruby DevKit is distributed as a self-extracting executable which simply dumps the DevKit in a folder, you can re-package it as a z7 archive.

Then in your Dockerfile you can RUN these steps but skip step one and replace step two with a call to z7 to extract the DevKit archive.

@vassilvk
Copy link
Owner

@woodie - to take your nanoserver-ruby image as an example, at this point here, instead of downloading the self-extracting executable of DevKit, you can ADD the DevKit z7 archive you've prepackaged and included with your repository.

@woodie
Copy link
Author

woodie commented May 26, 2017

Working with 7-Zip on Docker nanoserver images was a dead end, but there is progress.

As described here, I got everything working on nanoserver by doing a multi-stage build (passing through a windowscoreserver).

Please take a look at my nanoserver-ruby Dockerfile, and let my know if you think I'm doing something wrong by setting the path manually, and then calling dk.rb. There should only be one version of ruby in each container.

I'm also curious if there is any setup that should be included from the linux-based ruby Dockerfile.

@vassilvk
Copy link
Owner

It looks good - the multi-stage build trick is pretty cool.

I see no issues with hard-coding the path in config.yml -- you are in full control of the file system so there should be no conflicts or misconfiguration.

The linux-based image includes Bundler. Did you plan on including that with your image?

@woodie
Copy link
Author

woodie commented May 26, 2017

My goal is to have linux and nano base images appear identical from the standpoint of ruby, so I plan to enforce all the same versions of supporting tools (rake, gem, bundler) within reason. At the same time, I want to embrace the goals of DevKit to avoid stumbling across issues that DevKit has already resolved.

@vassilvk
Copy link
Owner

In this case I'd gem install Bundler and set up all the BUNDLE_* environment vars as per the official Ruby Docker image.

@vassilvk
Copy link
Owner

@woodie - I am closing this issue as there is no actionable item for the Slacker codebase.

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

No branches or pull requests

2 participants