9 ms·

Does Running Java on Docker Containers Violate Agreements?

36 points by ancatrusca 11y ago

wstrange 11y ago
Stick to OpenJDK, or zulu, and you are fine.
- chhum 11y ago
  If you use OpenJDK you can end up with an unknown version of Java - specifically whatever Debian or Canonical happened to pull from the source tree and ship, which in some cases have been automated top-of-tree pulls before. See for example: github.com/docker-library/openjdk/commit/00a9c5...
vkjv 11y ago
tl;dr: "...it is clear that distribution of these images may open both the users and the publishers of these images to public repositories to legal action." If you build your own images that include the Oracle JDK, host them in a private registry, and don't distribute them to 3rd parties you are probably fine. Otherwise, you may be in violation. I am definitely not a lawyer, but I don't see how this is something specific to docker. Wouldn't this apply to VMs as well?
- teraflop 11y ago
  Sure, but the default Docker registry is public, and Docker encourages you to create and publish images without any mention of copyright. The same argument applies to e.g. EC2 machine images, but AMIs are private by default.
- imtringued 11y ago
  I am not a lawyer either but it all boils down to distributing JRE + your software is okay but distributing the JRE alone is not.
- alblue 11y ago
  The difference with a VM image (or an .iso, for that matter) is that it contains both your program and the JRE in the same deployable unit, which is what the license permits. Docker containers, by contrast, store each layer separately, so that you can build up a runtime by overlaying multiple layer elements. Each software install results in its own layer being created and then pushed independently. This allows deltas to be shipped more efficiently since they only store the changes for each layer. However it now means that you're shipping the JRE separately from your application, which is against the rights given by the license.
seanp2k2 11y ago
If this is true, I really hope that it begins a mass abandonment of everything Oracle.
- zdkl 11y ago
  As a fanboy for clojure I have mixed feelings about this
  - KurtMueller 11y ago
    You could always use ClojureScript :)
    - zdkl 11y ago
      Definitely! I'd love a compile to rust-like target though, that would be something

36 points by ancatrusca 11y ago

wstrange 11y ago

Stick to OpenJDK, or zulu, and you are fine.

chhum 11y ago
If you use OpenJDK you can end up with an unknown version of Java - specifically whatever Debian or Canonical happened to pull from the source tree and ship, which in some cases have been automated top-of-tree pulls before. See for example: github.com/docker-library/openjdk/commit/00a9c5...

vkjv 11y ago

tl;dr: "...it is clear that distribution of these images may open both the users and the publishers of these images to public repositories to legal action." If you build your own images that include the Oracle JDK, host them in a private registry, and don't distribute them to 3rd parties you are probably fine. Otherwise, you may be in violation. I am definitely not a lawyer, but I don't see how this is something specific to docker. Wouldn't this apply to VMs as well?

teraflop 11y ago
Sure, but the default Docker registry is public, and Docker encourages you to create and publish images without any mention of copyright. The same argument applies to e.g. EC2 machine images, but AMIs are private by default.
imtringued 11y ago
I am not a lawyer either but it all boils down to distributing JRE + your software is okay but distributing the JRE alone is not.
alblue 11y ago
The difference with a VM image (or an .iso, for that matter) is that it contains both your program and the JRE in the same deployable unit, which is what the license permits. Docker containers, by contrast, store each layer separately, so that you can build up a runtime by overlaying multiple layer elements. Each software install results in its own layer being created and then pushed independently. This allows deltas to be shipped more efficiently since they only store the changes for each layer. However it now means that you're shipping the JRE separately from your application, which is against the rights given by the license.

seanp2k2 11y ago

If this is true, I really hope that it begins a mass abandonment of everything Oracle.

zdkl 11y ago
As a fanboy for clojure I have mixed feelings about this
- KurtMueller 11y ago
  You could always use ClojureScript :)
  - zdkl 11y ago
    Definitely! I'd love a compile to rust-like target though, that would be something