Because OpenJ9 could save 30% memory usage, I use OpenJ9 in my project. Now the AdoptJDKOfficial docker image did not maintain in the furture. Today I tried to migration my project from AdoptJDK docker image to eclipse-temurin, but I did not found any docker image about OpenJ9. I am seaching from internet and somebody told that the license problem, is there possible to use OpenJ9 in the furture? why did not support OpenJ9 in the
eclipse-temurin official? I search from internet but did found any explain about this.
TLDR: Look for Semeru instead of Temurin.
As you can see on the AdoptOpenJDK blog
OpenJ9 builds
Part of Eclipse’s agreement governing the use of the Oracle Java SE TCK,
requires that Adoptium does not release OpenJ9-based or GraalVM-based
runtimes. We know that OpenJ9 builds were very popular at AdoptOpenJDK,
and we are delighted to report that IBM has stepped in to provide
equivalent builds directly from their website.
Adoptium has plans to distribute multiple vendor builds of OpenJDK
in the near future, so keep an eye on the Adoptium blog site for more
information about that exciting adventure.
So what you are looking for isn't a temurin docker immage, but a semeru docker image. Semeru being the name of IBM's equivalent to Temurin with OpenJ9 (the version the AdoptOpenJDK blog talked about).
Both can be installed/managed e.g. via SDKMAN.
I installed Docker on a Red Hat Enterprise Linux Server 7.5 (Maipo) system:
docker version
Version: 1.13.1
API version: 1.26
Package version: docker-1.13.1-58.git87f2fab.e17.x86_64
OS/Arch: linux/amd64
Now if I try to run a docker image, I get errors similar to this:
docker run docker.io/jupyter/datascience-notebook
tini: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
I have searched for help and have already taken a multitude of possible actions:
libraries seem to be linked correctly
all libraries are up to date
Hello-World example works
I also came across information saying that running containers from docker.io / hub.docker.com under RHEL is not supported - which I don't really get, as main purpose of docker is to enable running programs independent from their OS...?
https://access.redhat.com/solutions/1408853 Does this mean using docker under RHEL does not really provide me with the possibility of easily deploying/sharing a docker-image with non-RHEL users?
Also, does this mean I can only access and use official RHEL-docker images?
https://access.redhat.com/containers/?start=90#/search/
As I wanted to use docker to have ready-to-go environments with R-Python/Jupyter/H2o (and similar), I'm disappointed because I could not find suitable images for RHEL there.
So, my questions would be:
Is it possible to run docker.io / hub.docker.com images under RHEL7.5?
if not, could I share my own created docker images under RHEL7.5 to other users with different OS versions?
Are there other projects / sites to share docker-images for data science purposes on RHEL?
Would you agree that my next step would be: building my own docker-image, adding R/Python/jupyter step by step?
Best regards,
workah0lic
This error message
tini: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
comes from within the container image. It could be a corrupted container image, but the message is also printed when the glibc dynamic linker determines that the kernel features are not sufficient for loading libc.so.6. I looked at the image (digest is sha256:79f929bd0e58fa9cb238dceda48b0c8360e748d09b476b429216c93dac0bd783), and it appears to require kernel 3.2, so the Red Hat Enterprise Linux 7 kernel version of 3.10 should be sufficient.
In fact, I cannot reproduce this problem with kernel-3.10.0-862.6.3.el7.x86_64 and docker-1.13.1-58.git87f2fab.el7.x86_64. You could try to run this command to obtain additional information about dynamic linker behavior:
docker run -e LD_DEBUG=all docker.io/jupyter/datascience-notebook
I am looking for mq v9 docker image for windows.But I am unable to find the link to run the image on docker.Instead I have seen the links where most of the tool expertise have explained about the mq image for linux.
If anyone is aware of this, please share the link, it will be helpful for me.
Thanks.:)
Assuming you are talking about IBM MQ.
There is currently no support for an IBM MQ Windows image. The only platform that is supported as a containerized platform is Linux.
Source: No mention of any other platform than Linux on the Configuring IBM MQ in Docker Knowledge Center page
Now in theory you could create one by hand using the sample MQ Dockerfile and config files available on GitHub as a basis. However if you encounter problems with this then you won't be able to get any help from IBM.
That said. If you are talking about running the IBM MQ Docker image on a windows machine (so the host machine docker is installed on is Windows) then you can still run the Linux image inside that docker. For windows docker installs a VM where it runs the images and this VM generally is Linux meeting the requirements set out on the Docker support on Linux systems Knowledge Center page
Docker installation guides does contain three different ways of installing Docker. I want to know the exact difference between the three components.
Docker CE (Community Edition) is the simple classical OSS (Open Source Software) Docker Engine.
Docker EE (Enterprise Edition) is Docker CE with certification on some systems and support by Docker Inc.
Docker CS (Commercially Supported) is kind of the old bundle version of Docker EE for versions <= 1.13.
Take a look at this blog post and this other one about Docker CE & Docker EE.
"What is Docker Enterprise Edition?
Docker Enterprise Edition comes in three versions: basic, standard and advanced. The Basic edition comes with the Docker platform, support and certification, while the Standard and Advanced version add additional features such as container management (Docker Datacenter) and Docker Security Scanning.
Docker EE is supported by Alibaba, Canonical, HPE, IBM, Microsoft and by a network of regional partners. Those who want to test Docker EE can download a trial version for free from the official site.
Docker is also offering a certification program to help third-party vendors in ensuring their products work with Docker EE.
What is Docker Community Edition?
Docker Engine has been renamed to Docker Community Edition, and, as the name suggests, it’s a do-it-yourself, community supported version of Docker that’s available for free of cost.
The community edition will be available in two versions: Edge and Stable. Edge will be released each month with the latest features. Stable will be released on a quarterly basis. While Edge will receive security updates and bug fixes for the current release, the stable version will get similar updates for four months after the initial release. This update cycle will give users a big enough window to plan upgrades from older versions.
While the two versions are targeted at different audiences, there isn’t much, or any, difference at source code level. “Both Docker EE and CE are based on the open source Docker project, which is developed in the open with Docker’s community of partners and contributors, and this forms the open, modular core of all Docker CE and EE editions,” said Messina."
From CIO.com
Also, take a look at the resources here and the official Docker documentation.
TL;TR;
We are currently dealing with two editions of Docker: Docker Community Edition (CE) and Docker Enterprise Edition (EE).
Docker EE comes with additional features that can help enterprises launch, manage, and secure their containers more efficiently, but what is worth emphasizing is that the two editions offer the same core features.
The main differences are that Docker CE is a free to use for everybady and open source and, on the other hand, Docker EE in the basic plan costs $1,500 per node, per year...
Another important difference is the operating systems on which we can run them. Docker CE can run on Windows 10 and Mac, on Azure and AWS, as well as CentOS, Debian, Fedora, and Ubuntu and Docker EE can run on Red Hat Enterprise Linux (RHEL), SUSE Linux Enterprise Server (SLES), Oracle Linux, Ubuntu, Windows Server 2016, as well as Azure and AWS.
Thus, in most private and commercial cases of Docker use, Docker CE should be sufficient.
For an in-depth look at all the differences, I encourage you to visit:Docker Community Edition or Docker Enterprise Edition - Everything You Need to Know
Docker CE vs EE: An Overview
Docker CE is a free and open source containerization platform. It is a rebranded version of the Docker open source solution that has been freely available since the launch of Docker in 2013.
CE can run on Windows 10 and Mac, on Azure and AWS, as well as CentOS, Debian, Fedora, and Ubuntu. CE can be downloaded directly from the Docker Store.
Docker EE, on the other hand, is a premium version of CE. Docker EE is an integrated, fully supported, and certified container platform that runs on Red Hat Enterprise Linux (RHEL), SUSE Linux Enterprise Server (SLES), Oracle Linux, Ubuntu, Windows Server 2016, as well as Azure and AWS.
Docker CE vs EE: How They’re the Same
First things first, it’s important to note that Docker CE is not a ‘watered down’ version of Docker EE. Both CE and EE have the same core features and functions:
Both editions are updated quarterly (although Docker CE users can expect “Edge” updates, discussed further herein), and both are available on a wide range of popular operating systems and cloud infrastructures, giving enterprises the freedom to run containerized applications on their favorite infrastructure—without lock-in.
Docker CE vs EE: How They’re Different
While both editions offer the same core features, Docker EE comes with additional features that can help enterprises launch, manage, and secure their containers more efficiently.
Here’s a summary of what companies can do when using Docker Enterprise Edition:
Gain access to certified Docker images and plugins
View your container clusters in a single pane view
Access controls for cluster and image management
Receive official same-day support from Docker
Run vulnerability scans on your Docker images
Run Docker EE engine with FIPS 140-2 certification
Advanced image and container management, LDAP/AD user integration, and role-based access control (formerly available only through Docker Datacenter, which is now part of the Docker EE plan)
Continuous vulnerability monitoring and Docker Security Scanning (formerly available only through Docker Datacenter, which is now part of the Docker EE plan)
Understanding Docker’s Versioning Format
As you research Docker CE and Docker EE, you may wonder about the platform’s versioning format. On the release of both CE and EE, Docker decided to change the way they versioned their product. Before March 2017, the latest version of Docker that was available at the time was v1.13. After the rollout of CE and EE, the new version was referred to as 17.03.
From the outside, it seemed as if Docker had skipped past 16 versions, but in actuality, Docker had changed their versioning scheme to YY.MM (year and month), similar to the scheme used by Canonical for Ubuntu..
How Often Are Docker CE and Docker EE Updated?
Docker CE comes with two release channels: “edge” and “stable”.
The edge channel releases a new version every month, and you gain the advantage of getting new features with each release. As for the stable channel, a new release becomes available every quarter.
If you decide to go for the stable option, you will have to wait longer to get the new features; however, on the plus side, the stable channel is much easier to maintain since you only need to install an update every quarter, as previously mentioned. The edge channel is suitable for those who want access to the latest features quicker.
In terms of support for both channels, the edge channel only releases bug fixes and security patches during the version’s current month. The stable channel releases patches for security issues and bug fixes for 4 months after the initial release, giving users a one-month window to upgrade to the latest release while still receiving fixes.
With Docker EE, a new version is released every quarter, and each release is supported for a full calendar year. Both bug fixes and security patches are backported to all supported versions.
Source: Docker
Docker CE vs EE: Pricing
Docker CE is free to use and download. The overall experience of CE can be enhanced through a range of free and paid add-ons from Docker Cloud at your own discretion.
Docker EE is a premium version that is available through three pricing tiers:
Basic: With Basic Docker EE, you get the Docker platform for certified infrastructure, along with support from Docker Inc. You also gain access to certified Docker Containers and Docker Plugins from Docker Store.
Standard: Comes with the same features as the Basic tier but with added advanced image and container management (single pane view), LDAP/AD user integration, and role-based access control (Docker Datacenter).
Advanced: Comes with added Docker Security Scanning and continuous vulnerability monitoring.
The general pricing for each tier is usually based on cost per node per year:
Basic: $1,500 per node, per year with Business Critical support
Standard: $3,000 per node, per year for Business Critical support
Advanced: $3,500 per node, per year for Business Critical support
Docker EE is also available as a one-month free trial. To activate your Docker EE free trial subscription, log into The Docker Store and navigate to the Docker EE page.
Is there anyway to build an image with Dockerfile while using Kitematic?
From the top of the docs for Kitematic
Legacy desktop solution. Kitematic is a legacy solution, bundled with Docker Toolbox. We recommend updating to Docker for Mac or Docker for Windows if your system meets the requirements for one of those applications.
If possible, you should avoid using the tool.
If you have to use Kitematic, the feature you are asking about is tracked by this GitHub issue: Import Dockerfile - (Docker build). At the time of writing the feature is not implemented.