8
hack
4y

Docker.

Even the getting started tutorial didn't worked correctly. It basicly ask you to run commands and fails to execute. I also banged my head to wall few times while trying to connect my dockerized application to database container.

Comments
  • 0
    Agreed. Learning docker from scratch was horrible. I forget exposing my ports to this day :^)
  • 0
    It also confused the hell out of me at first.

    Using portainer might help at first. It's a container that controls other containers and gives you a great web ui for docker.

    After I understood it, it made me addicted. Having tons of software projects in university/college made me want to do something else than coding in my free time.

    My favourite setup is now:
    - Nginx on host. Reverse proxying to containers.
    - Each stack (one or more containers that are called "services" at that point) in its own directory, with docker-compose.yml, numbered http port and all volumes in the same directory

    This makes some seriously portable services. Like extremely lightweight VMs that run on basically any Linux. Even most cheapo VPS servers (though check for it before).
    Also almost never any conflicts and I can't destroy my package manager with PPAs like I used to.
  • 0
    I did vagrant before I even tried docker, the few times I do try do setup docker i I keep ranting why it can't be like vagrant, so much easier.
  • 2
    docker-compose is such a pleasure.
  • 0
    100% agree.

    I STILL cannot see ANY usage for docker.

    In another rant I learn that it doesn't even OS independant (Linux container cannot run on windows).

    So WHY ? What's the "big idea" ?

    For me anytime I read "docjer", I read "Too lozay people not willing to build a VM".

    "Oh but you can run multiple docker in the same VM". yes you can. Why ? You share SLA between all your services. So not 1 will go down, but all of them.

    "Oh you can have different configs". I can also have multipel end pojn ts on a web server with more flexibility.

    Docker is just a buzzword.
  • 0
    @NoToJavaScript oof, hard disagree if you're serious. Docker definitely has its places and advantages.
  • 3
    Been using Docker for years now.

    Outside some rare "nanidefudge?" moments, it's the best thing I've discovered.

    So much nicer than having to build a VM from scratch for every project and/or hoping my SysAdmin is competent enough to have all the right dependencies.

    All I do now is tell SysAdmin to install Docker (which is literally a single command) and off I go.

    Everything runs dockerized on my server and development environments nowadays.

    Also scaling and HA goes basically effortless.

    Just sit back and let my Swarm figure it out by itself.

    Since I run Docker, the amount of downtime attributed to software (so not counting internet and/or power outtages) has basically been "no."...
  • 3
    @NoToJavaScript That seriously sounds more like you don't understand containerization to begin with...

    If you share SLA between all your services but think VMs are better, you're doing the Docker wrong.

    If you try to run Linux containers on Windows, you're doing the Docker wrong.
  • 0
    Well docker definitely has problems like handling of root privileges but I like to use docker as often as I can. Of course everything docker can do you can also do with a vm but with docker I e.g. can start and stop different dev environments on my local machine in seconds. Nothing a vm can give me.
  • 1
    @bosi pssst, and don't forget, it doesn't waste a few hundred MB of RAM just to have the bare VM running while you could have used that memory for running more services :^)
  • 1
    @NoToJavaScript Oh boy...
    Docker absolutely can run on Windows. Linux containers also run on Windows.
    Your other points are literally just you misunderstanding how you're supposed to use Docker and what it even is.
  • 2
    @bosi Take a look at Podman for a rootless replacement for the Docker daemon. ;)
Add Comment