I have a folder of MP3s, some of which date back to 1999, just a few years after the format was popularised. Most of them have utterly terrible names (think RIDEONAM.MP3). I think at this point they might even survive the heat death of the universe. And they’ll still be terribly-organised.
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?
I haven’t used secrets but I would go through the docker compose secrets docs
https://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.