Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
magicMirror705721djust 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.
Mandrake74121dDo 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:
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.
magicMirror705721d@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 :\