I think there's a misunderstanding.
In the docker-compose.yml, you specify services, and these services can use the official container images.
The only thing the docker-compose actually does is define your services so you don't have to specify them each time starting a container.
I've seen people posting that getting an instance up and running is difficult, so I hadn't checked it out. This looks pretty simple. Am I missing something?
My understanding is docker-compose is just a glorified installation file where you can install multiple containers and configure their interoperability/file systems/other config stuff, whereas images are the actual installation files for that specific container.
IE I can run a docker-compose to install App X, mariadb, and (IDK some third thing) at one time, but using images I'd have to install App X, THEN mariadb, THEN mysterious third thing, haven't had enough coffee lol.
You can run it from an image without docker-compose but I'd recommend looking into docker-compose if you're not already familiar with it. @[email protected] has the idea right that it's just a powerful installation file and can automate your docker management process rather well if you're using it a lot.
You can build a container from an image but it's obviously more hands-on. Lemmy may have additional dependencies they include in the compose file that may not be present in the image source. but starting with something like
A Docker image is a read-only template that contains the instructions for building a container. A Docker compose file is a YAML file that defines a set of Docker services.
A Docker image is a static artifact that can be used to create multiple containers. A Docker compose file is a dynamic configuration file that can be used to create and manage containers at runtime.
Docker images are typically used for building and deploying applications. Docker compose files are typically used for managing and orchestrate containers.
That came out of an AI. I can deploy images more easily on my NAS, and I've worked with them in the past, so I want an official container so I can deploy it alongside all the other docker containers I have running.
Docker Compose is just a tool to elegantly lay out containers in a stack. It's not a replacement for containers and images. If you need the image names themselves for use outside of compose like in a NAS GUI setting, they would be in the compose file.