Wednesday, March 16, 2016

Legal Usage of Oracle JDK with Docker

I have been a fan of Docker for a while now, and while it has grown out of infancy some things still feel like they can be a bit up in the air. One of the topics that comes up is that a lot of people are using Java. Now if you don't require Oracle's JDK that's find just simply install OpenJDK and that's fine.

Recently, the folks at Takipi made this post, talking about a practice that I would believe many people could be following. The long and short of it involves using a cookie to override accepting Oracle's License Agreement. This is far from ideal, potentially illegal, and while I don't endorse such action the likelihood of Oracle enforcing this for individuals seems unlikely. On the other hand companies are likely to be targets of such violations. In order to follow the correct procedures I have a very simple solution.

Manually download it from Oracle.

Amazing! I know! How could something be so simple? You're not by-passing anything, because someone is logging in and downloading the software just as you would if someone were to be setting up this software themselves. This practice extends any other Oracle software which requires this. Now I may get flak for saying this, but when thinking about it in a corporate context if an app is planning on upgrading to a new JVM that's going to require updating the Dockerfile regardless. Once this is manually downloaded it's placed on to some share drive where the build server will have access to the files. The additionally advantage is that every time you build your Dockerfile the JDK and what ever other files don't need to be downloaded.

Update (4/7/2016): I have actually confirmed this with sales people from Oracle

No comments: