Comment on Spotifies come and Spotifies go, but that folder of badly-sorted MP3s will still be there in the 2050s.

• notoftenthat@sh.itjust.works ⁨2⁩ ⁨days⁩ ago

  Switch “some script” to “docker compose” and you are a subject matter expert.

  source
• Sir_Kevin@lemmy.dbzer0.com ⁨2⁩ ⁨days⁩ ago

  all the learning resources just kinda assume you understood wtf it’s doing.

  Welcome to the linux community.

  source

  • Hawke@lemmy.world ⁨2⁩ ⁨days⁩ ago

    I mean I’d rather get told to “rtfm” than hear “it just works” with no explanation

    source
• r_13@lemmy.world ⁨1⁩ ⁨day⁩ ago

  I tend to think of docker containers like light virtual machines.

  You can start with an image of a very simple bare operating system, or from an OS with a few things installed (in my case I have lately been using images from dockerhub under nvidia/cuda-ubuntu so that my container spins up with ubuntu and the drivers and SDK for my GPU).

  Then essentially the Dockerfile becomes the sandbox from which to test installation scripts, see what works by trial and error if necessary, to install the programs you want – if you make a mistake or the install script fails as in the comment above, you can just kill the container and spin up a new one without the “doesn’t really work wrong but its never quite right again” issue :)

  I know this does sound like ‘rtfm’ but I definitely have made a lot of use of the Docker manuals: docs.docker.com/manuals/

  These manuals, plus stack overflow searching for Dockerfile tips, and github repos for the software I want to use that sometimes do contain Dockerfiles, have been enough to get me acquainted with spinning up my own containers and installing what I need, and use docker compose to run multiple containers on a single host that can talk to each other. Beyond that, I had to search a bit harder (mostly on StackOverflow, but also a bit of tail-chasing using ChatGPT) to learn how to configure overlay networks to allow containers to talk to one another from on different servers, and using docker stack to spin up a swarm of containers as services on a cluster.

  source

  • Hawke@lemmy.world ⁨1⁩ ⁨day⁩ ago

    Yeah… that all makes sense and those docks seem decent. The piece of the puzzle that’s missing for me is: how does docker turn a yaml config that says like … (from their example):

    > frontend:
    >     image: example/webapp
    >     ports:
    >       - "443:8043"
    >     networks:
    >       - front-tier
    >       - back-tier
    >     configs:
    >       - httpd-config
    >     secrets:
    >       - server-certificate
    

    … into actual operating, functioning container blobs? e.g. How does it know that “secrets: server-certificate means that it should take an ssl cert and place it in the container? How does it know where to place that certificate?

    source

    • r_13@lemmy.world ⁨1⁩ ⁨day⁩ ago

      I haven’t used secrets but I would go through the docker compose secrets docs

      docs.docker.com/compose/how-tos/use-secrets/

      At a glance it seems to be informative, but I’m not sure if it explains in depth how it is doing things under the hood.

      source