Docker Hub Reviews

- CI integrations available

- Cost effective

- Accurate and fast deployment

- Only for command line applications

- Very low uptime, making it difficult for storing data

- My work is depended on different container images

- I cannot install of them in my system, so I am using docker

- Lightweight, CI integrated can attach multiple different images and make my workflow more efficient

The simplicity of exchange of full docker files.

Nothing at all. I think it is one of the few very well orchestrated solutions.

It allows for the containerization of our monolithic applications.

Serving apps. Creating pipes. East deployment to production, easy to integrate different modules.

Cleaning docker images storages.

Hard to onboard

Serving apps in the cloud.

Help building pipes.

1. Its easy to use and work with the team members

2. Packages can be installed very easily and can be deployed to docker hub so that we could reuse that.

3. OS specific issues can be solved.

4. When we adapt dockers in our projects so multiple members can work together and also the package installations can be avoided so that is saves time.

5. It can be easilly integrate to the running projects

6. Docker containers can be saved locally as well..just like that it provides many features.

7. Its easy to pull docker containers with even single command.

1. It will consume the memory rapidly.

2.Low memory might result in performance of the system.

Docker can solve number of problems. We have used docker in many projects , so that when we commit a docker container to docker hub and team members could pull the container and make use of it and as one of the member had insttalled the required packages then the time consumption for that kind of applications can be reduced. We shall create work environments with in it , so that some projects needs linux environment or embedded based OS , so for testing and all we might dont have those devices with us , so we shall pull the docker containers which we used before and make use of it for modifications and testing. So that it shall help to work remotely as well and we could simply run linux environments in Windows OS easily.

Docker is distributed , helps to code independently in any platform , languages with seperate containers without any conflict.

Docker helps to build multi container application by docker compose, it gives techniques to build , integrate , and portable container images to run in independent platform.

There is nothing to dislike Docker. It is a well versed software for any cloud or non cloud developer. Faster migration, independent features, fast deployment, security therefore its preferable to used Docker .

Docker solves multiple problems as below-

Less programming knowledge also useful to use Docker . No extra cost for deployment lifecycle. Early release can be planned using Docker.For a cloud based application its like a urge to use Docker to deploy in cloud that means it gives scalability, no redundancy of code , extra security, code migration if needed , flebility of resource sharing etc.

It helps in reproducabilty of environments across our devolpment and production servers

Steep learning curve and server restart because of docker bugs

It helps in reproducabiliy of environments and quicks fallbacks in production systems

The best thing about docker is that its functions for package builds. As a developer, it has helped me transfer my files more efficiently by containerising them. It also has excellent help availability within the command lines. The documentation is also straightforward to understand and apply. Its versatility with various engines in development purposes makes it stand out from its competitors.

At the start of installing and running the docker software, it has become an issue while running that it shows an error; although it gets solved irritates developers. It would be great if they looked into it.

In the development field, when a code works on certain someone's laptop/pc, it doesn't work on the other pc so to overcome our organisation has come to use docker, where it containerises its code as well as the os, which in turn rectifies the issue of the above mentioned.

Can run on cross platform

Can build applications on OS based container or completely from scratch

Can tag images

Low resource consumption if configured well

Provide continuity of service if configured well

Very easy to use and implement

TUtorials available almost everywhere

Great user community

Registry available

Helps in contributing in Open Source

Used everyday

Nothing to dislike

One thing is that one needs some experience to work with it

We are using docker to host nodered, nginx, elasticsearch which is part of the magento stack

It makes it easy for us - Less administration of middlewares on OS

Image already available

it helps in saving time compared to traditional install

Docker a platform with which I can containerize my application easily it works cool with windows Linux and mac .My web app works on my machine and it works cool on my friends machine as well, only thing they need to do is that they need to run the docker image of my app that I had build and shared . It also provides volumes, networking through which containers can communicate with each other. It also has large registry called docker hub where all official images are stored.

Docker has only a single point of failure called Daemon server which means the commands that I run my CLI were executed by daemon server . If that fails there is no alternative like podman.

Main problem it solves is that it is light weight and has light weight base image and few app and os dependencies with which if app runs on my machine it works any where regardless of environment.

Its main functionality which is to simulate the best environments for a piece of code to run. If I can set up the right docker container that the author intended, I do not have to set up anything else. It removes the need for complicated setup instructions in many scenarios. The CLI is automatically configured to use the most popular CLI registry so I do not have to specify URLs.

The CLI can also be configured to work with ACR's CLI.

The number of image pulls a day is limited on the free plan, unlike Podman.

It is a bit complicated to set up a local registry for machines with large storage.

Sometimes, the platform error it gives on MacOS can be misleading for new users.

We use it to distribute components to each other for local testing through writing Dockerfiles. It saves time from setting up dependencies ourselves. We also share updates with each other through new images pushed to DockerHub or Azure Container Registry. The multistage building feature also allows us to reduce the size of the final image so a lightweight image can run the binaries. This way our storage does not get all used up.