You're welcome.. I've been using computers for around 40 years now, and love trying out new software. That evolved in trying out self-hosted software.. even into self-hosting nearly everything. I'm reverting some of that at the moment, don't want to self-host family stuff anymore because of continuity, but the rest I keep installing and trying everyting.. :-)
I pay for a hosting plan for my email for that reason. I should find a cheaper email centric option but SURELY I'll do something with those 2 other domain slots I paid for..........one day >.>
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.
Yes, but the benefit of an official image would be that I wouldn't have to recreate it when a new version was released, it would update itself when I reload the container.
I have a container running Watchtower and it checks once a week for any updated images so I can go through and update whatever needs updating myself. IIRC there's an option to have it automatically update stuff but I don't know nearly enough yet to be comfortable with that - If something is going to break let me break it myself so I can troubleshoot it haha.
I use Portainer as a GUI docker management system, and in regards to updating I can just hit a "Recreate" button and select "re-pull image" to update them. As long as you have the containers tied to persistent data folders it just pulls the latest image and ""re-installs"" it per your docker-compose file and everything is just as you left it.
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.
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.
I don't know yet how much time I will or won't spend on Lemmy, but I'm happy to lend a hand if needed. I've been on moderation teams a number of times over the years on various platforms so it's no big deal to me.
Hey I'm in a similar boat. Unsure of total time available, but hey I seem to spend enough on Reddit so I may have more free time than I realise ಠ_ಠ Happy to help out
I'm on a week long ban from Reddit anyway for checks notes "abusing the report feature" directly after the message saying that they agreed the linked report was in fact against TOS and actionable. haha.
"Yes, that comment WAS against the rules, but like could you stop asking us to do our jobs please?"
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. @CannaVet 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
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.
Won’t be long before you discover sonarr, radarr, overseerr, prowlarr etc and realise you need docker containers and maybe proxmox and it just goes on.
It’s great fun to tinker, come back in a couple of months and tell us what you’ve set up.
selfhosted
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.