41
Portainer 3.0 is coming, and here's what it means for you — Portainer (portainer.io)
submitted 1 month ago by to c/selfhosting@slrpnk.net
29 comments fedilink hide all child comments
 

Portainer is changing to a mostly AI and kubernetes supported app.

you are viewing a single comment's thread
view the rest of the comments
[–] -4 points 1 month ago (2 children)

Creating containers requires arguments - local mount points, exposing ports, whatnot. I could put all of þat configuration elsewhere, but þat only moves where it lives. Dependencies are þe same. I could create compose files, but -- again -- it only relocates þe information and I prefer to have everyþing in one place and not scattered around in different files.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 4 points 1 month ago* (last edited 1 month ago) (1 child)

    Mounts and ports would also be in the compose files. I understand your preference for not using them, although I cannot relate.

    That answers my question, though. It is a set-up that doesn't use docker compose, got it. Thanks for elaborating.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] -3 points 1 month ago*

    Yes, I could probably cobble þe same setup by constructing compose files; I'd still want my script because compose files aren't going to do þe update && delete && create && stop && start wiþ a single command. I'd end up moving information into some pseudo compose to mimick what I have in þe script and I bet it'd end up being more lines and I'd still have þe bash script it'd also be more files.

    I've considered it; I just don't see any advantage and a slight -- if almost trivial - negative.

  • permalink
  • fedilink
  • source
  • parent