34

Since I have started using Docker, I try to build even my local development environments around Docker...

DOCKER ALL THE THINGS!

Comments
  • 1
    vagrant up!
  • 1
    Try this on arm-servers. No chance to find images.
  • 0
    @heyheni Except that one is more like a Container and the other more like VMs, what would the main benefits of Vagrant over Docker be?
  • 1
    @YouAreAPIRate Fucking tell me about it.
    official Docker on Arm64 is horribly broken...
  • 4
    @FinlayDaG33k Vagrant is not a container technology so you cannot really compare it to Docker.

    Vagrant allows you to specify an entire environment in a text file and give it to someone else so that they can run exactly the same environment as you, it then uses templates to initialise VMs rather than containers. Plus by default it runs on VirtualBox, so, ya know :/

    It is cool though, the ability to have an entire environment built by only using vagrant up is staggering.
  • 1
    @Nhil As far as I have noticed, Docker allows me to do the same.
    I can create a docker file and build an image as I need (or use an existing one).
  • 2
    @FinlayDaG33k Just re-read your comment, sounds like you already know what Vagrant is :/ apologies...

    I still would not put it in the same category as Docker though.
  • 0
    @Nhil well.. in global terms they try to accomplish the same thing (correct me if I'n wrong).
  • 0
    @FinlayDaG33k I'm not sure, I have only really used Vagrant, but as far as I understand the point of Docker is to give you a platform that will minimise your overheads for separate services/applications. Whereas Vagrant is meant to allow you to rapidly build and share a development environment that mimics your production environment (at least that is what I get from their main web page).

    So I guess you could have a Vagrant file that builds/initialises a Docker image :/

    But Vagrant is too slow to use as a container/VM production technology, at least in it's default form.

    I prefer to use it with QEMU/KVM backend instead.
  • 3
    Theres a perfect blend of Docker, Vagrant, Puppet, to make a scenario where devs have a prod-like world and ops has a production environment devs don’t complain about . I just haven’t found the blend yet and I’ve been searching for ten+ years.
  • 1
    Thanks to D being right next to F on the keyboard, I usually write "focker" instead. Which leads me to immediately yell "run focker, run!"
  • 2
    @shellbug

    alias focker="docker"
    alias fucker="docker"
    alias d="docker"

    ;)
  • 2
    all my dev environments are docker too. Managed to convert 9 other devs at office to docker too. One bugger didnt convert. He resigned recently so all docker now. Recently set up a docker registry with LDAP authentication. Now setting up docker swarm for production.
  • 0
    @greenscar I'm still looking to get a registry going, but it's difficult since SysOps have a really shitty setup (3 physical machines running Windows Server...).

    also, our machines (with the exception of mine) are not built with our devs in mind, but with our students (so most things are locked down and files and programs are on a per-machine basis instead of just per-user, meaning if you switch PC, you don't have your files n programs).

    Our company is a huge mess when it comes to IT, but that's because they rather try to get the current shitstain working decently instead of taking everything apart and starting from the ground up with beter setups
  • 1
    true, sometimes setting things up from scratch is better than fixing the fucked up setups.

    Have you tried the official docker registry image on docker hub? It just works out of the box.
  • 0
    @greenscar yes, but didn't put it into prod yet cus I didn't trust the security of the out of the box install
  • 0
    @FinlayDaG33k The version 2 of the registry supports token based authentication. I haven't tried it myself but you could have a look here.
    https://docs.docker.com/registry/...

    Or if you want I can share my ldap authentication setup using proxy.
  • 0
    @greenscar think is, I want SSL, but the shitheads at work don't know how to SSL and unfortunately, that's not within my scope of privileges.
  • 0
    ooh. that's bad then. SSL certs from verified authority is recommended. Maybe you can try out self signed certificate but I'm not sure if it'll work smoothly. have to test.
Add Comment