ive tested both hydrus and monbooru’s ram consumption, and these were the results:

❯ ps aux | grep hydrus ghost_u+ 38817 0.0 0.0 3748 2204 ? S 21:45 0:00 /usr/bin/bwrap --args 40 – hydrus_client ghost_u+ 38832 0.0 0.0 3852 1356 ? S 21:45 0:00 /usr/bin/bwrap --args 40 – hydrus_client ghost_u+ 38833 4.2 3.5 4824044 261588 ? Sl 21:45 0:09 python3 /app/bin/hydrus_client ghost_u+ 39613 0.0 0.0 231268 2420 pts/0 S+ 21:48 0:00 grep --color=auto hydrus

❯ docker stats monbooru --no-stream CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS 0a46831f9470 monbooru 0.00% 19MiB / 7.047GiB 0.26% 13.6MB / 54.3MB 14.4GB / 5.51GB 20

      • thatsnomayo@lemmy.mlB
        link
        fedilink
        arrow-up
        0
        ·
        14 hours ago

        You are on the exact same kind of shitposting I am recently I guess. I have hundreds of these things & I don’t want them in my normal tagging system

        Nah not really it’s to show that this one will be making scheduled posts & I will abandon the inbox for long periods of time. Just means it’s off in the command line area rather than my phone most of the time. The db0 guy asked the same thing but he ignored me when I told him to pin lifeline4gaza.com so fuck him

      • vort3@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        1 day ago

        Because I don’t like docker. It’s one more abstraction layer that I don’t understand, going to spend time learning how to use it, need to maintain it, it’s gonna take up space on my SSD etc.

        Same for flatpak, snap etc.

        One developer thinks flatpak is the latest shiny hype thing ans releases his software as a flatpak. The other does snap. Third one prefers docker. Fourth one maybe something else.

        I don’t want to maintain this zoo of package managers on my desktop and think about “wait, was this app a docker or a flatpak, how do I update it?”. I want to sudo apt install everything because that’s the default package manager for my distro and I expect all the software to be in a repo that works with it.

        Not to sound entitled or anything, it’s just natural to not want to use docker imho.

        • ghost_laptop@lemmy.mlOP
          link
          fedilink
          arrow-up
          0
          ·
          24 hours ago

          well, i dont think it’s the same. docker offers an easier way to install and store this kinds of apps. for example i installed the arr stack which takes a bit of time configuring it, ive done it before but not with docker and i lost my data on reinstall, i know you can keep it but its not the same. docker stores all the dependencies there. you just docker compose up on a new system and you got the same app.

          regarding flatpak, also another issue. flatpak is distro agnostic, it’s not about being the shiny hype thing, but offering a solution to the linux ecosystem where devs needed to provide different package manager options. could there be another thing? yeah, but that could happen with apt too theoretically.

          • vort3@lemmy.ml
            link
            fedilink
            arrow-up
            0
            ·
            22 hours ago

            So, how do I use iptables to open ports for docker apps? Usually I install a thing that requires for example port 8080, and I open the port 8080. Does docker respect iptables?

            • ghost_laptop@lemmy.mlOP
              link
              fedilink
              arrow-up
              0
              ·
              18 hours ago

              this is my compose file for monbooru, ive added some comments to show you what each thing does, if you want to change the port simply change the the first 8080. all of these value:value mean that the first value is your machine, and the second one inside the container. that’s it, create a folder named monbooru, create a file named docker-compose.yml, add the thing i gave you below and save it. with your terminal cd into the directory where the compose file lives and do docker compose up -d and it will download the image and it’ll be runnin. believe me, i used to prefer to not use docker because i thought, ohh i have to learn to use docker, but honestly i wish i knew it was this simple long before so i wouldnt have done so many installs of some apps where i’ll lose my data

              services:
                monbooru:
                  container_name: monbooru
                  image: ghcr.io/leqwin/monbooru:latest
                  ports:
                    - "127.0.0.1:8080:8080"
                  user: "1000:1000"
                  security_opt:
                    - no-new-privileges:true
                    - label:disable
                  cap_drop:
                    - ALL
                  volumes:
                    - /PATH/TO/YOUR/GALLERY:/gallery
                    - ./config:/config #this one
                    - ./data:/data #and this one make the app data live next to the compose file, so that you can move the folder and the data stays there
                    - ./models:/models #use this if you add autotaggers, otherwise delete it, i'd try it without them first
                  environment:
                    - MONBOORU_SERVER_BIND_ADDRESS=0.0.0.0:8080
                  healthcheck:
                    test: ["CMD-SHELL", "curl --fail --silent --max-time 5 http://localhost:8080/health || exit 1"]
                    interval: 30s
                    retries: 3
                    start_period: 10s
                    timeout: 5s
                  restart: unless-stopped
              
              • vort3@lemmy.ml
                link
                fedilink
                arrow-up
                0
                ·
                16 hours ago

                Can you set up docker in a way that it does not mess with my firewall?

            • Ghoelian@piefed.social
              link
              fedilink
              English
              arrow-up
              0
              ·
              19 hours ago

              Docker automatically opens ports your containers need through iptables. Because of this, it bypasses rules set by ufw, which is great.

              Podman does not do this afaik, and since it only runs rootless it’s a lot less risky as well.

        • Peter Horvath@mastodon.de
          link
          fedilink
          arrow-up
          0
          ·
          edit-2
          16 hours ago

          @vort3 @gary_host_laptop Be strong. Docker is for the assholes of the todays to prevent them from learning Linux.

          It is a phenomenon in the German IT world. Meine Kollegen einfach boycotten Linux. Nicht, weil es komplex wäre. Es gibt ein einfach, stille Blokk.

          They are not stupid to it, they are simply assholes. As I feel, they might consider it somehow “non-conform” or so. And their hysterical drive for conformism is comparable to what you can read in the remembers of North Korean refugees.

          Docker is exactly for them.

        • Luke@lemmy.ml
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 day ago

          I just want to encourage you to reconsider. Docker (or podman) is worth taking the time to figure out. It’s not particularly difficult to learn the basics of, and is extremely powerful.

          Your life as a self-hoster will be massively simplified by spending a weekend learning to use docker or podman. Not using containerization is like opting in to hard mode with dependency and configuration hell.

          • vort3@lemmy.ml
            link
            fedilink
            arrow-up
            0
            ·
            1 day ago

            Yes but the app in OP clearly states it’s not meant to be open to the internet, it’s just a booru with web UI to be used on localhost. So it kinda has nothing to do with self hosting in a regular sense, why docker?

            • Luke@lemmy.ml
              link
              fedilink
              English
              arrow-up
              0
              ·
              13 hours ago

              You might be right about this software, but regardless of this specific use-case, I was responding to your overall sentiment towards containerization in general. It’s worth looking more into, that’s all!