I want to run Cloudera using a Docker image (specifically, the cloudera/quickstart image).
However, on Docker Hub I can only find beta versions:
https://hub.docker.com/r/cloudera/quickstart/tags/
What's the correct way of getting a more up-to-date image?
Should I just download a beta image and then install parcels? Would I do that using Docker Compose? If so, can I find instructions for that online?
Or is there a completely different way to solve this?
To run Cloudera Quickstart within Docker, follow the instructions on that page:
https://www.cloudera.com/documentation/enterprise/latest/topics/quickstart_docker_container.html
Forget about your concerns regarding the "beta" tag. These tags are there, because the Docker image of Cloudera Quickstart is in beta mode. However, the CDH version in there is not.
You will find this out on your own, once you run the container and check the CDH version inside.
Related
I was able to install docker, as well pull an image on my OS.
Went throughout most of the Docker Arch Wiki.
However now I wouldn't know what to do next. It would seem that the official docker docs mention just the Docker Desktop.
Perhaps I was expecting a docker image to work as a VM image. What I would like to accomplish here is being able to install Code - OSS without breaking the packages, and their dependencies, of my OS. Since Node.JS < 17 is required.
To my understanding, I could use the image and basically play with the packages there and if something breaks it's just the image that's broken, not my main OS.
Good Day:
I have been trying to create an Odoo 12 community version container on Docker in Synology DSM. Which source/tag should I use for this purpose?
The following source is the one I have been working with directly from Synology Docker:
https://hub.docker.com/_/odoo/
(Tag: Latest)
The only thing I have been able to do is creating a container for Odoo 12 enterprise, but not for Odoo 12 community.
Please advise.
Regards,
The official Odoo docker version is currently from date 2018-10-08 and it had a bug that showed incorrectly Enterprise version in Settings page also in Community version. So the good news is that you are in fact already running Community version. The bug was fixed in this commit.
The more complicated question is what version of docker image should you run. The official Odoo docker image (library/odoo or _/odoo or just odoo) does not get updated very frequently. It is not updated to fix issues. I would not recommend it for any other use than testing.
You can use other images that are updated more frequently and have static tags, e.g. I maintain an image with nightly Odoo builds. It is named veivaa/odoo. You can use a specific version of Odoo nightly build with tag version-date, e.g. veivaa/odoo:12.0-20181106. The nightly image can be found in Docker store at https://store.docker.com/community/images/veivaa/odoo. This version is updated on ”best effort” bases.
You find more information on running Odoo in Docker in my blog.
It is also not best practice with Docker to use the latest tag in production use or if you need to be able to keep the container stable. This is because you would get a different version depending on when you pull the image. Best practice is to either use a stable nonchanging tag, or build your own Dockerfile and image in own container registry.
I have a pod in which i have image ubuntu desktop i connect to this image via xrdp what i want to do is to add eclipse image to this pod in other words when i connect to this ubuntu desktop i can find eclipse.
I am going to create platform based on kubernetes with image catalog.
For example a profesor of java want only ubuntu desktop and eclipse. He gonna choose from catalog ubuntu and eclipse all backend i will do it myself.
So when a student connect he will find eclipse on ubuntu desktop.
You have to create an image from a dockerfile recipe that includes a command for installing the eclipse package.
Then you can use your own image for the deployment into the cluster (instead of the ubuntu image you are using today).
Please read up how to create a docker container and dockerfile documentation.
You can also take a look at an example dockerfile.
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.
I have a rhel7 host with docker in it.
I have build a image with also rhel7 as base image.
But when I run the container & do yum update or try to install in package with yum, it gives me below error.
"This system is not registered to Red Hat Subscription.you can use subscription manager to register"
I have already subscribed the host RHEL Machine. Do I need to subscribe each and every container with rhel image?
Or
Do I need to subscribe in the dockerfile itself while building the image?
Thanks
On the Docker hub, you can find some Red Hat docker images , like
https://hub.docker.com/r/richxsl/rhel6.5/
or
https://hub.docker.com/r/lionelman45/rhel7/
but in order to update them, you will need a valid subscription
You will find Red Hat docker images on the Red Hat site, at
https://access.redhat.com/containers
this article summarizes what you need in order to build a Red hat docker image
http://cloudgeekz.com/625/howto-create-a-docker-image-for-rhel.html
it begins with
Pre-requisites
Access to RHEL package repository.
With RHEL 8 Red Hat now offers a universal base image for docker containers which does not require a subscription.
The RHEL 7 documentation covers this. Please use your subscription to read section 1.4.
Paraphrasing what the documentation says:
You must use a subscribed RHEL 7 host to build containers
Containers based on RHEL 7 will use the host's subscription automatically and be able to access the RHEL 7 yum repositories
If you are trying to build RHEL 7 based containers on a properly subscribed RHEL 7 host and it doesn't work, you might be running into a bug. I would contact support to try and sort this out.
I used podman to pull RHEL 7 Universal Base Image, like this:
podman pull registry.access.redhat.com/ubi7/ubi
After that, although I still saw the warning message:
This system is not registered with an entitlement server. You can use subscription-manager to register.
but there was no issue to use yum for package installation or update.
You can also use RHEL8 ubi in the same approach without any issue.
I found this article that clarifies the RHEL UBI images which do not need a subscription.
https://developers.redhat.com/blog/2020/03/24/red-hat-universal-base-images-for-docker-users/
docker search registry.access.redhat.com/ubi
docker run -it --name test registry.access.redhat.com/ubi8/ubi:8.1 bash
I tried yum to install a netcat command which worked seamlessly
The RHEL UBI image contains 3 default repos (see yum repolist). Subscription is required for the CodeReady repo (ubi-8-codeready-builder).
If you decide to NOT subscribe then you can hide those warnings with:
yum --disableplugin=subscription-manager install <package>
Source:
https://developers.redhat.com/blog/2020/03/24/red-hat-universal-base-images-for-docker-users/