Comment

I recently ditched Portainer entirely - it looks good, but debugging anything is really not helpful. And if it runs on the first try I don’t need a web interface.

My tips:

Run self hosted things on Linux and open their webpages on Windows if you really want or need to keep using Win.
Prefer docker compose “stacks” over docker directly or native installs. Personally, I just use 4 sub-commands for pretty much everything I do: up, down, pull and logs. You (probably) don’t need Portainer.
If after 1. making sure the docker-compose.yaml is right, 2. setting up the .env file if present, and 3. following the instructions in their README; a container stack doesn’t run after 2 or 3 attempts: copy the error message and search the GitHub issues - chances are someone else also faced that problem. If you can’t find anything similar, open a new issue.

source

Sort:hotnew top

Melco@lemmy.world ⁨1⁩ ⁨year⁩ ago
[deleted]
source
- talbot@lemmy.world ⁨1⁩ ⁨year⁩ ago
  It’s essentially a GUI for Docker. It has its own quirks that, in my opinion, don’t match Docker’s UX and can make it more complicated to customize deployment. But Portainer can make multiple environments or dozens of containers easier to manage. e.g. I do most of the actual work using compose yamls but use Portainer as a reference to organize subnets, ports, and volumes. Or if I’m unsure what the problem is and just want to see all the details of each container faster.
  
  source
- zbecker@mastodon.zbecker.cc ⁨1⁩ ⁨year⁩ ago
  @Melco @eager_eagle
  I never used portainer. Imo KISS is the best policy
  source