• 30 Posts
  • 3.84K Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle

  • Well, that’s a new development. That used to be the go-to method they pushed. Thanks for pointing that out.

    As for Docker Desktop being the top option, it would only be used for a “development environment” because why would you install that on a headless docker host for production? And after the horror stories I’ve heard of Windows and Mac versions of Docker Desktop, there isn’t a chance in hell I’d use it anyway.

    So yes, going forward it looks like adding the repos and apt-get install are the way to go. Except, the convenience script was so… convenient.






  • That Community-scripts seems to come off as some sort of Proxmox association, but I can’t see anything official. Maybe Tteck is endorsing it, but it’s not clear either.

    Keep in mind that running scripts, especially curl-bash pipes, has a huge security risk as anything can be substituted in the scripts or the dependencies they call. No clue who MickLesk is and not saying they’re good, bad or indifferent. But there is no reputation there and caution should be exercised.








  • ikidd@lemmy.worldtoSelfhosted@lemmy.worldHelp with docker setup
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    1
    ·
    17 hours ago

    When I tried it last (a couple years ago), the docker snap was an untroubleshootable mess. I don’t like the idea of running Docker that way, in whatever version of a container that Canonical has come up with for snaps. It’s just looking for problems. Run an application with Snap if you want, but a whole container system? No thanks.



  • ikidd@lemmy.worldtoSelfhosted@lemmy.worldHelp with docker setup
    link
    fedilink
    English
    arrow-up
    12
    ·
    edit-2
    1 day ago

    Debian with the docker convenience script. Stay away from Ubuntu server, for the love of dog.

    Make a folder such as /stacks and put everything there by building docker compose stacks. I bind mount everything local to a subfolder with the docker-compose.yml for that application so when I restore it, it’s all in one spot, not spread all over the hell like docker likes to do if you don’t use bind mounts.

    Add lazydocker for getting easy log and stats access for each stack.

    Avoid bare docker run commands. It makes an unmanageable mess when you get more that a couple containers running.

    Consider using the nextcloud AIO master container. It runs docker containers inside a master container compose file, and it is by far the easiest way to manage and run nextcloud.