"For our app we are using Docker, so for the new server we will need a barebone Linux install"
"Oh please no, Linux is not for a stable server and is very hard to manage, let's install Windows Server 2002 and you can virtualize everything you want"
"Wait, we really can use our cpu cycles to something better..."
"Sorry, too late, already installing!"

Our sysadmin is a Microsoft integralist, we should RUN!

He is a “sysadmin”

Poor soul

To be fair, if the os doesn't matter for the application itself, I prefer having my sysadmin knowing the os rather than using whatever I like and make his job harder

@FMashiro true. Still, the target of the app was chosen months ago. He had plenty of time to bring his ideas to the table. We picked everything toghether. Still, he gave us a "Hyperv is better than bare metal" after months of Dev work.

@FMashiro to be fair it's Windows server 2002 (or 2012? Typo?)

@beegC0de you are right, my bad.
A little update: last day we bought a 2016 license (our 2012 is actually... ehm... unregistered) in order to accommodate his needs, but the poor thing was not comfortable with the new version.

Talking in general talking bad about the sysadmin just because he prefer windows doesn't make you any better... Talking in topic the problem was that they agreed on the specs and the sysadmin didn't say anything till last minute... Anyway both os cluld be the best choice in different scenarios

Talking about docker, were you planning on Clustering it? If so which method you prefer? Kubernetes, docker swarm, etc?

I'm going to put the dot on this in case 1) it turns into a Windows bashing party, or 2) it turns into a Docker automation discussion. :)

.

@coderme screw Windows let's talk about container orchestration

@ahmadhsalim Bring it! I'm looking into Portainer for automating a few dozen websites, but it looks like a pain to set up.
What about database servers? You obviously wouldn't want a separate MySQL container for each website, right? Or would you?

@coderme I think I would want separate containers. Isn't that one of the main purposes of containerization? Isolation.

@coderme we're looking into container orchestration. Docker swarm is quite easy to setup but I'm looking into kubernetes but it's more difficult to setup. It has certain networking prerequisites in order for it to work. The default docker networking isn't enough. Have to use third party networking solution like Google Compute Engine or Flannel.
Haven't looked into Portainer.

@coderme docker swarm doesn't support auto-scaling yet

Looks quite complicate to manage this on linux with docker, how is it compared to Windows server?

@dontbeevil on windows server you would basically create a linux vps and do the exact same thing except with extra virtualization overhead

@dontbeevil docker swarm is very easy to manage.

@greenscar For services like mysql, I (not knowing docker) assume that 100 separate containers for 100 separate databases would be too much overhead. Instead I'd assume a single MySQL container running as a service, and autoscale to add more if necessary. Don't know.
Portainer looks pretty useful, it's a GUI for scaling docker and it has graphing and so forth for container performance. Looks easier than Kubernetes to me.

@coderme I see.
Yeah I just ran the Portainer docker image. It's pretty cool. But it doesn't serve the purpose of kubernetes.

https://www.docker.com/kubernetes
Yippee Kubernetes coming to docker out of the box. Can't wait.