Right now it looks like you can only run lemmy in docker-compose, is there work on an official container?

  • ericjmorey@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    That came out of an AI

    is that why it doesn’t quite make sense to me?

    Can you make a container from the compose file?

    • Svengarlic @lemmy.worldOP
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      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.

        • Svengarlic @lemmy.worldOP
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          I mean, I know I don’t have to recreate it when I use a normal container, but I’m not clear when using compose

        • CannaVet@lemmy.worldM
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          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.

    • Terrasque@infosec.pub
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Think of container as a running VM. Image is the file system of the VM. The image itself is static, so when restarted alll file system changes get tossed out (you can map certain paths inside the container to other storage). A Dockerfile is a file that describes how to build the image (For example : Use an ubuntu base image, run these commands, copy this file in to this path, expose this network port, and when running the container, start this file when it boots up).

      When running a container you specify which image it should run, network ports to expose to the host network, environment variables that should be set inside the container, if it has access to a gpu, mapping paths to storage and so on. You can even change the startup command.

      A docker compose file is a config file that can define all those things, and define it for multiple containers, binding them together in one stack. So you could for example have a static web server, an api server, a database server, redis, and so on defined and configured via environment variables. And you could just do “docker compose up” to bring up all the parts in their own docker namespace and virtual network.