A lot of docker containers.

I often have to use docker containers while I don't understand it as well yet and quite some containers literally come with zero documentation or bad docs.

This both as for how to set the containers up and how to debug stuff.

This is one of the big reasons why I'm not as big of a fan of docker yet.

just exec into the running container, and look around.
Most of this stuff is built on top of alpine - or someother light weight base image - so just "exec -it" into it, and look around

It takes a bit of doing, but once you master docker-fu, it dramatically reduces the time it takes to stage environments.

@magicMirror
There's also dive:
https://github.com/wagoodman/dive

It can be a little slow if you have a massive number of layers, but will eliminate the need to stage a container to view layer contents.

Do the servers have documentation?

I'm not able to see the relation between the lack of documentation and using or not docker.

Here is an example of good documentation of four docker containers required to run Jitsi Meet:

https://jitsi.github.io/handbook/...

But yes, both in regards to Docker and Docker-Compose, as well as several pieces of software shipped in Docker containers, the docs are awful far too often.

@magicMirror I've seen images built on top of Ubuntu, which is not exactly lightweight.

@kescherRant
Most of Microsoft's garbage containers are built on Ubuntu server. Thankfully it's easy to retarget.

@kescherRant Are you working in my company????

The idiots here (devs) have no idea what is Ops. On the other hand the Ops morons have no idea what the dev guys are up to. Also, they can't code to get in out of the rain. I'm the only one who understands what devops even means.

so - all our images are debian+compilers(!)+git(???)+ffmpeg - and use static compiled binaries.
Base image before adding compiled binary? 1.1Gb. 🤦‍♂️

I love Docker but yea, I do get you, a lot of containers are poorly written and/or poorly documented :\