Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
Please explain the difference between Containers, Docker and Kubernetes.
Who owns them and how can we learn more about these new technologies
Container : Package Software into Standardized Units for Development, Shipment and Deployment.
Docker: Docker is enterprise container plaform which use to create the container and container images.
Docker is a set of platform-as-a-service products that use OS-level virtualization to deliver software in packages called containers. Containers are isolated from one another and bundle their own software, libraries and configuration files; they can communicate with each other through well-defined channels.
There are also some platfrom like docker for example rocket which can be also use to create container images and container.
Kubernetes : Kubernetes is comes under the CNCF organization. Kubernetes called as k8s which is open source project.Kubernetes is orchestration tool which use to handle and manage one or more containers.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
Previously, I used Virtual Box to launch a second operating system on a computer. But it was very laggy :( After learning about docker I was interested, can we run other ubuntu on docker on ubuntu? In particular, with graph interface.
Docker does not has an “OS” in its containers. In simple terms, a docker container image just has a kind of filesystem snapshot of the linux-image the container image is dependent on. All Linux distributions are based on the same kernel, so you could, for example, run a filesystem based on Ubuntu in a container.
A container/image could contain an Ubuntu filesystem snapshot with something like this:
FROM ubuntu:21:04
However, the container is not in and of itself a virtualized environment in the same way that a Virtual Machine is.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
As a new starter in the world of DevOps, I've tried to find a one-pager that explains side by side what each of the following technologies do best and how they are orchestrated together in typical deployment scenario.
Its all a bit overwhelming coming in cold.
Seems like there's a technology for every single step of the deployment. Have some been superseded by others? Are the differentiated in the granularity of the artifact?
No opinions please of which is better, just resources of hey they are used together.
Docker
Kubernetes
Helm
Terraform
Rancher
Docker is the de facto standard for building containers and running them in various environments.
Kubernetes is a complex framework for orchestrating containers.
Helm is a component of Kubernetes, a package manager for running apps on Kubernetes.
(Rancher is a framework for managing and orchestrating containers. It could also manage Kubernetes clusters)
A typical scenario 'devops' scenario would involve builiding Docker images from source, and running them in A kubernetes cluster in production, as described in a Helm chart. The underlying infrastructure for Kubernetes could be deployed with Terraform.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I am a bit confused about Docker EE. In my case I have fully working setup of Kubernetes. It has few dev,test application containers, and now we want to move for production containers(App) which are client facing so developers were talking about docker EE for prod. Now how it will affect my existing kubernetes infrastructure? Do I need to go for any additional configuration for my kubernetes, or it's just way of creation of container image by developer part will change?
As existing Kubernetes infra maintaining part is anything changes?
DockerEE has its own way to install and setup kubernetes.
Its simpler than the usual kubernetes setup in my opinion. But one thing i noticed in dockeree, kubelet is running as a container managed by swarm. Most if not all kubernetes control plane components are managed by swarm not systemd.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
How to create two docker images, one with service A, one with service B. Both images should also contain a consul agent, when complete, they should be able to startup and discover the services in the other image.
See docker-compose
Docker compose allows you to defining and run multi-container Docker applications. With Compose, you use a YAML file to configure your application’s services. Then, with a single command, you create and start all the services from your configuration.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I need to decouple my single monolithic application to "micro services" and each module is a combination of (application server + database).
Wondering out of this
Vagrant
OpenVZ
Docker (not preferred choice as it doest not support data persistence)
which one is used in production servers ?
TL;DR: Docker and RKT are enterprise choices, Docker has much wider community, attention and impelmentation.
First of all, Docker supports data persistence. You can easily do this via volumes, and lots of drivers available for different storage backends.
Docker Philosophy: Microservices.
Google started using containers in 2000s, Lots of enterprises use containers under heavy load today. Docker is one of the best implementations there is. So Definitely docker depending on your needs and environment.
Vagrant is for development environments. You can even use docker inside, or no vagrant local docker.
OpenVZ has focussed on setting up VPS containers that you decorate yourself manually. Therefore they provide templates for empty linux machines that you can start up and shut down, that you afterward SSH into, to set them up yourself with whatever you need, like a LAMP stack.
OpenVZ vs Docker: OpenVZ sees a container as a VPS, and docker sees a container as an application/service. So definitely docker for microservices.
RKT, functionally docker is all similar to rkt; however, along with "Docker Images", rkt can also download and run "App Container Images" (ACIs). Besides also supporting ACIs, rkt has a substantially different architecture that is designed with composability and security in mind.
rkt has no centralized "init" daemon, instead launching containers directly from client commands, making it compatible with init systems such as systemd, upstart, and others.
rkt uses standard Unix group permissions to allow privilege separation between different operations. Once the rkt data directory is correctly set up, container image downloads and signature verification can run as a non-privileged user.