The setup is easy and simple. 

Mirantis Container Cloud's deployment takes around two days to complete. 

The initial setup is easy. I would rate my experience with the initial setup a ten out of ten, with ten being easy to set up. 

The deployment took a couple of hours. We're actually using Azure Cloud for container deployments.

We don't have a private registry. Any images we deploy already exist in our private tenant registry, so pulling them is quick. Mirantis Container has a repository we can enable and install from. So, deployment time really depends on whether the parent image already exists elsewhere.

The setup is straightforward. The deployment takes only one day. I need a virtual network or virtual server to deploy the product. I prepare DevOps scripts, implement the Ubuntu operating system, and implement the Docker environment. After that, I implement the software.

The solution is deployed on promises. We are also implementing it in the cloud environment in Microsoft Azure. Azure is expensive, so we will soon migrate to Amazon. The implementation is easy for us because we have a skilled DevOps engineer.

It's straightforward, but there is a certain level of complexity when you're deploying anything on a server level. That is applicable to all containerization platforms such as OpenShift or Tanzu, but you get great support from Mirantis for setting up everything.

It can be done within three working days. The deployment process is pretty basic. Before deployment, we need to have a complete idea of the infrastructure and the customer's needs. We need to know the kind of infrastructure they have and the workload that they would be running. Based on that, we do the sizing and deployment.

It can be deployed by one or two engineers. Even one engineer can get it done. Its deployment is straightforward.

Deployment time varies depending on the cluster configuration. Sometimes, it can take days. It depends on the configuration of the clusters. In some cases, like the configuration assessment can take longer. But that's not because of Docker itself.

It's just because we might not have information about the Docker configuration, for example. Let's say you have a cluster in another Kubernetes environment, and you want to use a port from that other cluster on your current Kubernetes cluster. That can make things more complex.

The setup of Docker was very straightforward. Maybe for a beginner, it may be difficult. If you are in a Windows 7 environment, it's very difficult. Some of our systems are in Windows 7. As soon as we ran Windows 10, it was easy. If Docker was run on Linux, Mac, or any Unix product, it was pretty straightforward.

The entire pipeline is for eight teams. If you're pushing all the way through, it takes about four and a half hours including the test execution. There are around 100 test cases, including the unit tests, that need to be done for a simple change. That was taking about three days.

We were able to push through in four and a half hours by including NetWare. For our implementation strategy, we used a Docker-based continuous integration/continuous delivery pipeline.

Depends on the environment and what you need to use. Most of the features have full online documentation with live examples.

The initial setup is pretty easy. I think it's super easy with the universal builds offered by Docker for ARM64, Linux, Windows, etc. Even for people who are not familiar with terminal and text files, you can use the Docker Desktop UI to manage all your running containers, images, and modify your Docker daemon JSON file. I think it's really easy as a starting point.

The initial setup is straightforward but requires some knowledge and research to be executed properly. Once you understand the process, it becomes simple, involving configuration in one file. It is easy to reconfigure

Google provides us with GKE, a managed global cloud Kubernetes engine. We've deployed our application there. It's familiar territory for us, and scaling up or down is incredibly simple. Our workflow revolves around GitHub actions and a specific set of configurations. 

Mirantis Container Cloud's installation is straightforward and is completed in half an hour. 

It's pretty straightforward. It was easy to install on Windows rather than on a MacBook. On the MacBook, it was a little difficult, probably because of the version that my company is using. We had a little bit of confusion with that.

Everything was done onsite.

I would rate setup 4 out of 5.

The initial setup is easy and takes a day to complete. The process involves downloading an executable profile, which is available online, and then executing it on the machine. It requires following guidelines from the CACD team for setting up applications.

Docker installation is very straightforward because you can easily install Docker Engine based on the instruction provided on the Docker website. It is an easy four or five steps process. 

If you have good knowledge about the installation process, it can be installed in five minutes. However, if you do not have any information about the prerequisites of the installation, it can be difficult. You need to provide lots of prerequisites, such as install services. Without previous knowledge, it could take four or five hours.

The setup was very easy, but if you get into something with the backup agent or the API, that is when you may begin to stumble. Sometimes this causes a slower time for implementation and ultimate deployment. 

Our standard procedure is to look at the requirements, set of a pilot, do some testing, and then release the solution. It can take several weeks, and it depends on understanding our customers' needs. We have our own staff who complete the process.

The setup was very straightforward. I just followed the documentation on the Docker website, and it went smoothly.

Implementation for the client was not very big. It was eight to ten developers, and it took between one and two days to complete. The most important thing on our end was to get our client's infrastructure up and running with Docker.

One person can handle the deployment and maintenance of this solution.

It was straightforward for us. 

Initial setup was extremely simple and was done in minutes.

The initial setup of Docker on the Mac is simple. There is a very friendly GUI installer. If you already have Homebrew installed, you can simply run “brew cask install docker”.

Installing Docker on Linux is a different story, since the versions supported by the default package manager sources are out of date. It’s necessary to follow somewhat lengthy instructions from Docker’s website.

The initial setup was really easy and the deployment was fast and straightforward. I did everything myself.

The product's initial setup phase is simple.

The solution is deployed on an on-premises model.

Initial setup of docker itself is very simple.

Deployment of Docker is easy, it only required one person.

The initial setup is fairly straightforward.