What would have to change to the Dockerfile to build on RedHat version (say) 7.2

[oscar6echo]

I plan to deploy nbviewer on a corporate LAN, the http://nbviewer.jupyter.org/ being service unreachable from there.

Only RedHat images are available internally.

So to build the image, I understand that in Dockerfile

FROM debian:jessie

should be changed to

FROM <RedHat image name>

and command apt-get should be changed to yum.

Anything else more subtle ? Will nbviewer run on RedHat just the same.

I know the question is trivial, but maybe somebody has already faced the issue and can briefly give their feedback.

Thx

[bollwyvl]

@oscar6echo thanks for the interest!

Yes, it should work fairly similarly! With RHEL 7, you should be pretty good w/r/t to upstream python.

The LOCALE stuff might be different.

Rather than hacking directly on the Dockerfile, you might want to create a separate one that pulls down the github archive zip and does the install from there.

I've also been tinkering with conda recipes for many of the upstream dependencies... some of them are pretty sticky, but we might have a much smaller install footprint soon.

Let us know how it goes!

[christophelec]

Just to come back on this request, I worked with @oscar6echo and @laurentgrangeau to set everything up in our environment.

As expected, the main difficulty was to retrieve all the dependencies, since we do not have easy access to the outside world. Once it was done, NbViewer worked like a charm !

I put some infos on what we modified here : https://github.com/christophelec/nbviewer/blob/corporate/Corporate.md along with some example conf files (in the branch), in case it can be useful to someone else.

A lot of conf must be filled with info dependant on the corporation (mirror addresses, certificates, etc...), but the bulk of the work is done.

[parente]

Many moons later: this would be great to include in documentation if we get a ReadTheDocs site off the ground here.