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.
Related
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
I'm new to Terraform and just did all the Tutorials i could find about it. I have set up Multiple Docker Containers and a Network, Currently starting it with a shell skript. The general plan would be, to be able to start my testbed and all its components with Terraform (Like ONOS with containernet, Routers, ...).
My First Question would, is Terraform made for that kind of Question? Or would you suggest anything different. I thought using Terraform would make it Easy to write new Scenarios.
AT this Point I use the Shell skripts to build and run the Docker Containers. Does it make sense to let Terraform do the RUN (not build) task?
Thanks for your Help & Opinions
I'm new to Stack, it would be awesome if you explain a downvote - so i can learn to do it better.
edit ( Build file deleted - unnecassary)
The general plan would be, to be able to start my testbed and all its components with Terraform
Tl;Dr
Don't do this.
This isn't what terraform is for. Terraform provisions infrastructure. So (as an example) if you want an azure function, you write a terraform file that describes what this looks like then run terraform to create it. It doesn't (nor should it) run your function. It simply describes how Azure should create these structures prior to them being ran.
It seems you actually want a build pipline that uses terraform as part of that process to provision the infrastructure. The build script would then run the containers once terraform had done it's job
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 3 years ago.
Improve this question
I am trying to deploy my flask application with on docker with Redis as a container. I have docker-compose and everything setup and running. I am not running docker swamp though.
I keep reading conflicting information on the internet about the best way to deploy Redis on production. Some are suggesting supervisor and others Elastic Cache.
I am more interested in how to manage Redis and restart workers automatically if I do not use docker swarm.
I am new to the deployment world and I am little confused as to the best way to deploy my application.
I am deploying my App on AWS EC2
ElasticCache is only relevant if you're hosting your application AWS, but ElastiCache gives you two options of using Memcache or Redis anyway, so not much is changed there. ElastiCache is basically just a wrapper around Redis or Memcache, much like ECS is a wrapper around Docker.
I don't see what the problem is with having your Redis running off of a container in production.
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.
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.