Package Details: portainer-bin 2:2.37.0-1

Git Clone URL: https://aur.archlinux.org/portainer-bin.git (read-only, click to copy)
Package Base: portainer-bin
Description: A lightweight docker management UI (STS)
Upstream URL: https://github.com/portainer/portainer
Keywords: docker management monitoring webui
Licenses: zlib
Conflicts: portainer
Provides: portainer
Submitter: bbrks
Maintainer: envolution
Last Packager: envolution
Votes: 17
Popularity: 0.62
First Submitted: 2020-03-08 04:00 (UTC)
Last Updated: 2025-12-11 02:10 (UTC)

Latest Comments

1 2 3 4 5 6 Next › Last »

p01arst0rm commented on 2026-05-04 22:46 (UTC)

@envolution can package be bumped to 2.41?

aequilibrium commented on 2025-07-24 13:28 (UTC)

@envolution No I mean you're right, that's why I edited the override to be localhost, Im just saying having the default be all addresses is a dangerous, which as I mentioned before is how portainer itself handles it, the webgui doesn't let you configure the address to bind container mappings to xD. Just something to consider, to make the default config somewhat safer.

envolution commented on 2025-07-24 06:10 (UTC)

@aequilibrium see section 2.3 of https://wiki.archlinux.org/title/Systemd for the correct way to override provided systemd service units. It's always important to configure services like this to suit your environment. I'd also suggest some sensible firewalling if binding to a port is causing your service to be accessible to networks you'd prefer not have access.

aequilibrium commented on 2025-07-24 02:17 (UTC)

I really suggest altering the portainer.service to *, I've been using this package for a while, and its really convenient way to manage docker visually, but exposing that webgui to every address posses excess security risks no? If someone requires it on others, they can just modify the overwrite with systemd.d, or more hackily, they can just tunnel the webservice to a different address when necessary.

* [Service] Environment=BIND=127.0.0.1:9000 Environment=BIND_HTTPS=127.0.0.1:9443

But it seems the portainer team generally doesn't even consider this an issue. Their provided gui lets you map ports for a container, but it doesnt let you specify the address you'd bind it on. Its a lil backwards. But atleast the login portal wouldn't be exposed.

(one last bit of rant) They let you expose an http service, but are happy to transmit it on all NICs

JPT48 commented on 2025-07-04 11:36 (UTC)

hi. probably dependency fakeroot missing? thanks

envolution commented on 2025-05-21 21:36 (UTC)

LTS versions moved to aur/portainer-lts-bin

This package will track STS versions going forward

envolution commented on 2025-05-19 07:32 (UTC)

while 2.30 (STS) has been released, there are some issues related to proxy authentication (https://github.com/portainer/portainer/issues/12690) that I'll be waiting for a solution or patch to before bumping

stasadev commented on 2025-05-02 07:02 (UTC)

When version is bumped again, set pkgrel=1, see wiki.

envolution commented on 2025-02-12 21:33 (UTC)

@pika02 thanks for your report. Updated to 9000

pika02 commented on 2025-02-11 09:17 (UTC) (edited on 2025-02-11 09:18 (UTC) by pika02)

the port in .desktop file should be 9000. 9443 resulted in 400 Bad Request.