Page History

...

The installer fetches the latest Java binary via wget.

Most of the time, the download fails because either the firewall blocks it or because the cacher doesn't allow it.

Since Java updates are not very frequent, we can turn off the firewall while installing, but the cacher can at least be configured for a permanent bypass.

Create /etc/apt/apt.conf.d/03java-bypass with the following contents:

...

This will ensure that downloads from download.oracle.com initiated by pre/post-install scripts do not go through the cacher.

The ideal solution would be to make them cached but that needs a regex hack for apt-cacher-ng (to stop it from rejecting this site as a cacheable source) which I was not able to develop yet.

A workaround has been found for this problem:

According to this http://askubuntu.com/a/503992

One can add the following pattern in the acng.conf file.

PfilePattern = .*(\.d?deb|\.rpm|\.drpm|\.dsc|\.tar(\.gz|\.bz2|\.lzma|\.xz)(\.gpg|\?AuthParam=.*)?|\.diff(\.gz|\.bz2|\.lzma|\.xz)|\.jigdo|\.template|changelog|copyright|\.udeb|\.debdelta|\.diff/.*\.gz|(Devel)?ReleaseAnnouncement(\?.*)?|[a-f0-9]+-(susedata|updateinfo|primary|deltainfo).xml.gz|fonts/(final/)?[a-z]+32.exe(\?download.*)?|/dists/.*/installer-[^/]+/[0-9][^/]+/images/.*)$

However the trick is to help acng to send a HTTP cookie with each and every request so the following pattern is also necessary in acng.conf:

RequestAppendix: Cookie: oraclelicense=a

Architecture

If your host architecture differs from LTSP chroot, you won't be able to install Java this way. Chrooting will make the chroot report the host's architecture to the installer, which causes it to download the wrong binary. Generally, chroots should be kept the same architecture as host, but if they must be different, one can still install Java this way if live-boot from the correct architecture media is done and chroot is entered from it.

...