Docker

“finalizing task while running in isolated environments (we use docker for that)”

“I put all my build tools in a Dockerfile... I can't use it if I ask the LLMs for docker work since they need the docker socket”

“I've been using docker since the early days. One of the early choices I made and stuck with is to never let Docker touch iptables.”

“I ran 2 PoCs from GitHub today ... although I used the same Docker images and all”

“The agents are running inside a docker container (this is part of the setup)”

“It builds Chromium in a Docker container using Debian and spits out an AppImage.”

“the box keeps a warm Docker cache and doesn't cold-start every job.”

“our docker images build faster”

“Nowadays devs ship container images anyway through a CI so it is less of an issue.”

“organisation announced migration to Podman across the board”

“when we switched from LXC to docker I had to show ROI”

“For containers we run a standard Docker engine inside a special machine.”

“Somewhat adjacent in how I look at using Docker at all in prod”

“fork bombs by college/school students bringing out docker environment.”

“Takes some scripting to SSH port forward to docker port forward to the container”

“It started when we migrated to Docker more than a decade ago - before docker-compose was a thing”

“coming from docker, you still have that expectation... this has been my experience. I felt very stupid”

“I have been using Docker for installing NPM modules in interactive projects I was testing out. I believed Docker blocked access to the underlying host”

“flinging java, docker and a few other things onto a build agent isn't the time-consuming part”

“when I wanted to do anything with docker in production, not even at scale, everywhere said I should just use kubernetes.”

“mostly I deploy Docker containers to various managed services on AWS - Lambda, ECS, etc.”

“It's readable, declarative, and required no new tooling on our side since we were already using Docker and Terraform anyways.”

“huge Docker image sizes that slowed down boot times of our ephemeral workers”

“I'm still stuck with 3 bitnami charts that I keep updated by building from source, which includes also building the images”

“That isn't present at all in prod, or when running in k8s or docker compose locally.”

“I'm running a docker container though so YMMV.”

“Today, our multi-million dollar revenue company is using your memory allocator on every single service and on every single Dockerfile.”

“we're using a simple FastAPI server running in a Docker container.”

“I wrote a dashboard of web servers and docker container management”

“I was an early adopter of Docker (because Python) and I immediately hit the "now how do I run it in prod?" question.”

“I'm working on a project that has ~22,000 tests that operate on Docker container of the same version of Postgres used in production.”

“If I want to tinker, I do what I always used to do; use docker (podman and distrobox on fedora).”

“The server runs in a docker container which has an ssh server installed and running in the background.”

“I've been using docker professionally and at home for 5+ years now and know it very well”

“most of which was spent wrapping my head around Docker and Mesos that we used to run the .jar.”

“Every docker image we push to the registry has a version like trunkVer”

“I lost a chunk of my life writing 'dockerctl' and a bunch of puppet code that deployed it so it could manage docker containers as systemd services.”

“we switched to a Docker workflow and it was just doooooog slow on the Intel Macs.”

“it's just anything except those being redirected... we needed that for the way we use docker in development”

“now i write ml code and deploy it on a docker in gcp”

“At our org we run code-server in docker with no network access except pre-allowed DNS”

“remote Docker server instances to build new versions of apps”

“Then we'd run a Docker container on a machine. Startup time: 0.01 sections.”

“Same domain registrar with same API based on the same docker configs etc.”

“Yes I run local docker containers, though not with huge production datasets or for load testing or whatever—all that works fine.”

“The FIRST thing we do in every single repo is make a dockerfile and docker-compose.yml to easily work on things”

“deploy projects (they simply contain scripts, a dockerfile, helm values, etc.) most of which is boilerplate.”

“I have used a number of orchestrator platforms in production, including AWS ECS (Docker + custom orchestration)”

“bind-mount (read-only) to the Funkwhale-Docker inside an LXC container.”

“The Dockerfile is simply FROM linuxserver/wireguard:latest.”

“The test code respected the environment variables and connected to prod instead of docker.”

“wrote a web IDE and backend using Docker's REST API and Openresty”

“We run CI in an image generated by our devcontainer Dockerfile.”

“We use their Docker container support (to get ffmpeg, mostly) and it's been pretty smooth running throughout.”

“I mean this is more of less what using a local container for Postgres is.”

“That's part of my Docker setup, which is not in the repo”

“the current auto-deploy only updates container images”

“docker containers inside the VM losing network connectivity for the third time this week because the bridge decided it didn't want to do anything”

“Those include building docker containers, pulling down CMS databases for local development”

“When Docker Desktop hit, we moved to podman.”

“Java, Spring, grab the DB driver, write the query or use some ORM to do it, build a docker image, and it's done.”

“I've been using a TinyTinyRSS instance on Docker.”

“builds and pushes a docker image with a dedicated tag”

“because we basically spawn a new docker container for each build”

“If you (or someone in this thread) like self-hosted Docker stuff”

“I did spin up a local instance with docker compose and you get some integrations not available in the cloud hosted version.”

“dockermail for email (but not yet automated forwarding and filtering).”

“Just upgrade your dockerfile, or your ansible setup and reinstall it all.”

“Designing and writing the code to make things work locally and in a Docker container (running Docker compose) was pretty easy”

“I currently have it running in a Docker container on my Synology NAS.”

“we run it in a docker”

“reinstalling Docker, all sorts of rubbish.”

“We were already using Docker in CI, so we didn't need to spend much time making our app work in Docker for production.”

“The company I'm at did a migration from Heroku to Beanstalk... Biggest change was dockerising.”

“simplify our docker images which have a lot of legacy code”

“yes I do docker for a living for last 10 years, since v0.4 (lxc) days”

“I only use scratch in prod.”

“we use Docker locally to spin up our local dev environment”

“We use poetry just for development, but run Docker containers in prod.”

“We use docker but not Kubernetes.”

“it's also hard to say we run podman on the desktop but docker in prod.”

“running a dockerized Jenkins instance (and agents) in AWS”

“this was causing issues when we wanted to generate docker images for some of our packages”

“we tried to get their app running locally in docker. their app needed to use a dev instance of a db”

“after we switched the executors to docker-in-docker, was a pain to figure out”

“to send your docker to Lambda for inference and Batch/Colab for training”

“When we switched from docker to podman we immediately noticed how slow our container based build stage had become.”

“Of course we switched to Docker at some point.”

“We use docker for everything though, and have a single nginx listening on 80/443”

“Nice writeup, and at the core not too different from what I'm doing myself (albeit with the server at home”

“Just to name the ones we use at Helsinki City.”

“I host it on a raspberry pi in a docker container and have had no issues whatsoever.”

“with the option to run it locally via Docker for the times I need to dip into making sure specific bits run there fine”

“build step-by-step guides on how to launch a docker container through it”

“Our stack is based on all docker containerized python.”

“We have jobs executed against user specified Docker images on the user's chosen cluster.”

“I just did an update and release 1.1.0 of my docker image with support for pgTAP from 9.6 to 14.”

“I ended up making a docker image that we now use at work”

“we build our docker images on our CI which is on premise”

“the CI itself (running off Docker image) has to build a Docker image and push it somewhere”

“So essentially now i can run everything i need with a single Docker container.”

“It restarts the docker container to recover since I haven't had time to investigate.”

“a bunch of random workloads using docker, exec, raw_exec, java, and some in-house drivers”

“Two issues with it are having too many dependencies (so we run it in Docker)”

“it's a distributed as a docker container, so it's pretty easy to deploy”

“all of these old school RPM/DEB folks suddenly need to start doing docker.”

“We run a stupidly simple (though small scale) gitlab instance in docker”

“Recently started running Docker+ZFS in prod, haven't seen it break yet but appreciate heads up”

“i started by simple wrapper around docker 8 or so years ago.”

“We constantly look to upgrade our systems and processes starting from colocated servers finally to docker and aws hosting”

“builds and deploys ephemeral docker, CDK, and terraform based apps”

“Complementary tools and technologies: Docker, docker-compose, Docker Swarm in prod”

“the Docker step isn't strictly speaking necessary for the deployment, it's more for devs with diverse OS's”

“configure apps via some mixture of pre-baked amis, docker files and some sort of parameter store. (Usually SSM or Vault).”

“probably hadn't used Docker on my previous Mac in over a year”

“I too have been using Docker for a while, and recently also for certain programs on my desktop”

“we use Docker a lot”

“With the remote interpreter, we use Docker, I can debug code that is running on our servers.”

“I spent the entire weekend updating MaraDNS's Docker testing container to run Ubuntu 20.04 instead of CentOS 8”

“we run almost everything in Docker now”

“This is a problem with Docker because if your main app container needs to be restart it involves stopping Docker Compose”

“inside VM we run docker and docker-compose.”

“mirrors Docker images between two registries. ... coordinate external dependencies between Docker->GitLab registries”

“we deploy them all in Docker containers on AWS basically.”

“how to transform a docker only deployment into k8s deployment”

“So the CI-script for deployment is just a `docker build` command, the dockerfile of which clones a specific commit hash”

“We have a .buildkite to control the build, we have a makefile, a Dockerfile, a docker-compose file”

“We run this in a docker container with SQLite database”

“by first getting them ported to ASP.NET Core and then into Linux containers.”

“I then lead another whole project to migrate all the developers from an old dev server with issues to a new shiny dev server using Docker.”

“which led to simpler and easier to follow Dockerfiles”

“which runs when the Docker container starts. The DB file can be found in the data folder.”

“The main issue is you can't run Docker on WSL. You have to install Docker for Windows and connect your WSL docker daemon to it.”

“I've been using podman instead of docker more and more recently”

“Everything is in docker containers.”

“We use rocker docker image with xgboost and plumber, data.table to do pre prediction data wrangling.”

“hosting our own pre-generated vector tiles from Open Map Tiles in a docker image”

“The second part of the video is a guide on how to setup Raspberry Pi from scratch and install Docker on and it and make it ready for some production work.”

“It's a docker container now so not too hard to deploy.”

“when I built the Docker file with a tag of :latest and then ran the CF Template”

“inside one mssql docker container that is spun up for each test run”

“we switched from our home grown open source cartridge approach and dropped it to Dockers homegrown based approach in RHEL and OpenShift”

“On the most drastic end, we run each browser and server pair inside its own docker container.”

“Data scientists have a similar docker image running in kubernetes”

“Dockerfile with a tiny little web server gets deployed through or CI/CD pipeline for serving.”

“We started using docker and kubernetes not long ago. Every deployement in production must have a release number as a tag.”

“The app is made up of two Docker containers: the indexer and the webserver.”

“I'm using the Dockerized version and apart from increasing the version number in the Docker Compose file”

“we run an Ubuntu 12.04 Docker container (the Steam runtime), which runs an Arch Linux chroot in order to gain a modern cross-compiler.”

“Api-gateway -> Lambda -> NATS -> docker backend on GPU”

“For me my top memory consumers end up being: 1. Docker (web dev servers)”

“Spin up a fresh Postgres instance on Docker using -P to claim an available ephemeral TCP port”

“even through a Docker for Windows volume on really big applications with thousands of files, such as a Rails app.”

“Dabbled a bit with Docker and Kubernetes on Azure”

“production/dev setup with Docker and docker-compose”

“We run the exact same Docker image that ran in CI, the environment is the only thing that changes.”

“We're using .NET Core 2.1 in prod on Linux Docker containers.”

“required me personally to spend three full days refactoring code and resolving Docker issues due to an obscure error”

“we build packages (debs) and dockers, for deployment within VMs.”

“Key projects we utilize: ... StrongSwan Docker”

“Jenkins will spin up ~50 concurrent EC2 instances running docker”

“We just use a requirements.txt for each service and run pip with the -r flag in the dockerfile.”

“Build all artifacts, docker images, helm charts, etc.”

“we were running these tests all on one machine including a docker-composed test harness”

“the generated artifacts (jars and Docker images) are pushed to our artifact repository”

“we use the same docker image in both the deployment and evolution job”

“We have an extensive pipeline that builds Docker images using Google Cloud Container Builder”

“we run a docker instance of Chrome using tabs for multiple pages”

“We run it in our proxy-only environment pretty regularly. You want docker to have proxy settings but not kubernetes.”

“I have dotfiles with a "install-docker" and "install-vmware" aliases that installs it whenever I need it”

“start up the container on your mail host with all of the fun features turned off”

“teach them how to ding make targets inside of their docker containers”

“We run one docker container/build on docker swarm. Each build gets its own isolated/clean environment.”

“docker run --rm williamyeh/wrk -t4 -c100 -d1m --latency --timeout 2s http://10.131.45.89:8080/tykbench/get”

“the storage is on the same physical machine (in fact a shared docker volume) as everything else.”

“we use composer for installing components at build time with Docker (not on your host system directly)”

“Increasingly we are moving towards vagrant and docker for our development of the backend code.”

“these are numbers comparing the official images to these images we built using the standard Python benchmarks.”

“built my own 3.6 images a couple of weeks back. Here's the Dockerfiles and readme”

“The docker image is also built and released automatically from github on every official release.”

“we run nginx and certbot in Docker too?”

“In the past we've run full Chrome in Docker containers”

“People send a docker image (3d rendering, financial analysis...) and we run it on heaters deployed in buildings in Paris”

“The script skip takes the last successful build and retag the docker images to the current one.”

“We have a 9GB+ docker image that we create containers from some 10k times per day for our users in production.”

“We are starting to build simple docker containers for python via RHEL SCL version”

“it was not fit as a single-user instance with those 3-5 docker containers and stuff.”

“We also deploy (CI and prod) on docker for convenience.”

“Self-hosting is not complex although I wouldn't want to do this without the docker they offer.”

“I use it on docker hosts too, but w/e”

“I'm building a CI pipeline, E2E tests and "Dockerizing" an existing Java-based project management product”

“less if I fire up Docker, Visual Studio or heavier apps”

“We're using packer to create images/docker and then distribute them automatically via kubernetes”

“I was under the impression that everyone used the fully featured official docker image”

“Another way would be using the shell executor where we actually loose some functionality. (we use the docker executor).”

“working for Amazon right out of college, I've been using things like Bazel/Docker/Travis for 5+ years now.”

“so that we can run k8s components and a docker daemon cross platform (windows, osx, linux)”

“I've had experience in using Mesos & Docker in prod (running a 200 node cluster).”

“our strategy is to have two dockerfiles for each repo.”

“Managed to dockerize a few trivial .Net apps using the dotnet onbuild base containers.”

“promoting the exact same docker image from staging to production”

“In one year we migrated a full set of micro-services into a new infrastructure based on Kubernetes and Docker.”

“I work for a large company that used docker in production.”

“I've been using Docker in production for over a year now.”

“We use Docker containers in production, not right across the business, but in many important and up-and-coming areas.”

“The article clearly states we ran docker in PRODUCTION for 6 months.”

“I do use Docker, but it requires to learn Kubernetes or DCOS to do anything production-related.”

“I am actually building this on top of Docker, so technically that's already implemented (I'm actually testing this locally).”

“I think it's a pattern in docker to try to keep your containers as atomic units of your app architecture.”

“have been contributing to Docker and other Go projects for almost 3 years”

“we run into size of images needed for each container as well”

“some of it is derived from my experiences as a perhaps-foolishly-early adopter of Docker in prod at my previous gig”

“an old Docker Toolbox installation left some environment variables preventing Docker for Mac from starting.”

“We've built automation around our CoreOS baremetal deployment, our Docker container building (Jenkins + custom Groovy)”

“Our runner image has docker, we run our tests with docker-compose, if they pass we push them to our existing registry.”

“The primary fluentd service pulls the logs from Docker”

“using our Docker setup, which is another reason why it exists”

“We run Docker instances on those servers.”

“We run across difficulties with logging, version control of packages, speed, size of docker image, build time etc.”

“We run a sharded+replicated mongo cluster and a redundant postgresql array in docker containers.”

“On the master, the api-server, controller and scheduler all run in docker containers. On the minions, the proxy and kubelet both run in containers.”

“we switched to JAR/Docker deployments for Scala some time ago with Jetty instead of WARs”

“To achieve this, we use docker as well as an heroku inspired deployment approach.”

“our docker instance is really designed towards letting people play with it quickly”

“with enough disk space for Docker and VirtualBox... so my Docker images are compatible”

“the docker containers mount subfolders of that shared folder into the container.”

“We then use our production docker image(s) with some more development appropriate configuration options.”

“we use Vagrant so that we can run our docker cluster either locally or on Amazon”

“so you need to be careful to remember to do $(boot2docker shellinit) and expose container ports”

“every time you launch a docker container, it will register with consul and be added to haproxy”

“We mainly use Docker containers for testing / training, etc. ... so in production I'd never use Docker.”

“we have a host running docker for services that are contingent on an NFS mount”

“We export use Docker to build and export an image, then use CoreOS + systemd-nspawn to run it”

“One problem that we run into was security when started to use Docker. The management did not want to upload the images to any cloud provider”

“Our compute servers are blades with Debian VMs running Docker containers Of our applications.”

“We run SELinux on all our docker hosts”

“the last time I used it in prod, aside from Docker”

“Install in a dev docker and test it. Ship docker to production once I understand it.”

“We don't change anything in the Dockerfiles, it's more that we use the dependency logic in Make”

“just use an Ubuntu image with docker as my virtual dev environment.”

“one of things that have kept us from moving fully in the direction of Docker”

“we can continue to deploy Docker through Mesosphere Marathon onto Mesos as we've been doing.”

“We've been doing quite a bit with Docker on ARM for a while now, have experience with systems in production”

“We now use mesos+marathon(+chronos for deployment) for running our docker container”

“Each instance we run is usually a live version of a specific image (Amazon AMI or Docker)”

“all of the services run within Docker containers”

“For some projects we are creating containers with Docker and will need to get some things into production”

“sysops monitoring and provisioning (docker)”