Today's the day, I'm learning how to use Docker for local web development. It only took ~4 years to get the gumption.

Don't worry. You will love it so much, you will go back to your old ways of local development where everything works on your machine but not after deployment.

Don't be that guy that says it works on my machine after his deployment breaks production app. Docker is your friend!

@AjDevNull that is what vagrant/VM is for, not docker.

Docker is most useful if you deploy your stuff to containers.

Developing in a container and deploy to a VM or server that does not use your container is nonsense.

I am still refusing to use containers, but I am tempted because I am using gitlab runners a lot and will use gcloud container registry soon.

So yeah, lesson on docker coming up.

@mundo03 Yes. I inadvertently assumed if you choose to use docker for local development, you intend to deploy your stuff as a container.

@AjDevNull thank you. I like you now.

I haven't played with docker, but I just read this:

https://hackernoon.com/docker-is-de...

Is this really a thing?

@Demolishun

http://unikernel.org

It's a thing. Yes.

But to compare it to containers is ... Dumb.

Of course someone can compare apples to pearls, but it's obvious one is an apple and one is a pearl.

A unikernel runs it's own kernel afaik as it is a highly specialized virtual machine.

A container is something differerent of course....

As we know, a VM is seperate from the host, while a container shares a lot with his host.

Meaning: Unikernel is another paradigm, but as the docker ecosystem (or better containerd ecosystem) is so large it's unlikely to end and the approach of unikernels have their own problems.

There's no silver bullet as always.

@Demolishun i loved it.

Why would using Docker for running local environments be a bad idea if it works and simplifies things for me? I don't understand what the downside would be in practicality.

What am I missing?

(Serious question, implying nothing.)

@thehappyhipster there is no downside as long as other devs aren't involved and the Dockerfiles are linux based.

Depending on complexity, some system require changes in e.g. system variables (ulimits, kernel settings, etc).

When many devs are involved, this becomes a troublesome adventure.

Same for maintaining the environment, e.g. assuring every dev has the same docker / docker compose version.

@IntrusionCM Ah ok, I get that. That makes sense. Although that does very rarely apply to my usage case so I'm going to try it out either way.

(Not the least because someone told me not to. muhaha.) ^_^

@thehappyhipster here's my ultimate advice.

Don't listen to what people say, try out stuff If you feel like it.

Building own experiences is the best way to learn stuff and not become an old hobo screaming: "that's not how we did it back in my days".

@IntrusionCM Yup. That's solid advice.

@Demolishun I fucking hope so. Docker is the suck