Package Details: portainer-bin 1:2.14.2-1

Git Clone URL: (read-only, click to copy)
Package Base: portainer-bin
Description: A lightweight docker management UI
Upstream URL:
Keywords: docker management monitoring webui
Licenses: custom:zlib
Conflicts: portainer
Provides: portainer
Submitter: bbrks
Maintainer: bbrks
Last Packager: bbrks
Votes: 10
Popularity: 0.38
First Submitted: 2020-03-08 04:00 (UTC)
Last Updated: 2022-07-29 17:48 (UTC)

Latest Comments

LoopBack commented on 2022-07-14 23:54 (UTC)

2.14.1-2 works . Thanks

bbrks commented on 2022-07-14 09:45 (UTC)

@LoopBack should be fixed as of 2.14.1-2

Sorry, they keep changing the docker-compose path around under the hood with every single version!

LoopBack commented on 2022-07-14 03:37 (UTC) (edited on 2022-07-14 03:40 (UTC) by LoopBack)

Hello , I can no longer start portainer even after upgrading to 1:2.14.1-1. I get this error:

Jul 13 21:22:30 arch portainer[4467]: time="2022-07-13T21:22:30-06:00" level=fatal msg="Failed creating compose manager: docker-compose plugin is missing from config path"
Jul 13 21:22:30 arch systemd[1]: portainer.service: Main process exited, code=exited, status=1/FAILURE

I attempted @angellusmortis 's fix but I get file already exists.

bbrks commented on 2022-07-01 14:00 (UTC)

@angellusmortis thanks for the heads-up! I should've checked after the most recent update but was in a rush.

I've pushed an update to the PKGBUILD to use these new paths

angellusmortis commented on 2022-06-30 18:16 (UTC) (edited on 2022-06-30 18:17 (UTC) by angellusmortis)

Fix for 2.14.0:

ln -s /usr/lib/docker/cli-plugins/docker-compose  /usr/share/portainer/docker-compose.plugin
ln -s /usr/bin/docker  /usr/share/portainer/docker

flying-sheep commented on 2022-04-01 11:31 (UTC) (edited on 2022-04-01 11:31 (UTC) by flying-sheep)

Great, thank you! I don’t use that either, I just saw that portainer fails to start if there’s something using port 8000. Now I can use it!

bbrks commented on 2022-04-01 10:55 (UTC) (edited on 2022-04-01 11:10 (UTC) by bbrks)

@flying-sheep Got it. I don't use the Edge Agent feature, so didn't even know it existed.

I'll push an update to expose as an env var in the service script so it can be overriden in the same way as BIND using TUNNEL_PORT

flying-sheep commented on 2022-04-01 09:56 (UTC)

@bbrks no, that’s the UI port. I know that one can be overridden. I’m talking about the --tunnel-port for which you don’t specify an env variable.

bbrks commented on 2022-03-13 14:40 (UTC) (edited on 2022-03-13 14:42 (UTC) by bbrks)

@flying-sheep The service script defines port 9000 by default but can already be overridden.

Use sudo systemctl edit portainer to set the BIND environment variable with an portainer.service.d/override.conf file.



flying-sheep commented on 2022-02-27 08:56 (UTC)

Hi @bbrks, can you please make the tunnel port configurable?

I need my port 8000 for something else.

bbrks commented on 2022-02-15 12:22 (UTC)

Portainer have been screwing around with the 2.11.1 release a lot and it now looks like they've completely pulled it.

Will roll back this package to 2.11.0

markc commented on 2022-02-15 11:35 (UTC)

The latest version at Github seems to be 2.11.0, not 2.11.1

endlesik commented on 2022-02-10 19:18 (UTC)

Same as for Yura121, checksum for portainer-2.11.1-src.tar.gz became invalid

yura121 commented on 2022-02-10 11:27 (UTC) (edited on 2022-02-10 11:28 (UTC) by yura121)

==> Получение исходных файлов... -> Найден portainer.service -> Найден portainer.png -> Найден portainer.desktop -> Найден portainer-2.11.1-src.tar.gz -> Найден portainer-2.11.1-linux-amd64.tar.gz ==> Проверка файлов source с использованием sha256sums... portainer.service ... Готово portainer.png ... Готово portainer.desktop ... Готово portainer-2.11.1-src.tar.gz ... СБОЙ ==> ОШИБКА: Исходные файлы не прошли проверку целостности!

==> ERROR: Source files failed integrity check!

flying-sheep commented on 2022-02-07 23:11 (UTC) (edited on 2022-02-07 23:12 (UTC) by flying-sheep)

Could you please make --tunnel-port configurable in the same way as --bind=$BIND already is?

I have a service running on localhost:8000 and want to keep it there.

bbrks commented on 2021-11-01 13:05 (UTC)

@bwrsandman done, I guess they made docker-compose a hard requirement at some point :(

bbrks commented on 2021-11-01 13:05 (UTC)

@MrSoup678 I can build and run fine without npm... can you paste the error you're seeing?

bwrsandman commented on 2021-10-31 00:34 (UTC) (edited on 2021-10-31 00:35 (UTC) by bwrsandman)

The package fails to start without docker-compose. I suggest you move it out of optional.

Oct 30 20:18:15 my_hostname portainer[383]: level=info msg="2021/10/30 20:18:15 [INFO] [main,compose] [message: binary is missing, falling-back to compose plugin] [error: docker-compose binary not found]"
Oct 30 20:18:15 my_hostname systemd[1]: portainer.service: Main process exited, code=exited, status=1/FAILURE
Oct 30 20:18:15 my_hostname systemd[1]: portainer.service: Failed with result 'exit-code'.

MrSoup678 commented on 2021-08-06 17:36 (UTC)

Please add npm as dependency. This won't build otherwise.

ng0177 commented on 2021-07-26 19:51 (UTC)

@bbrks: works like a charm :-)

chenghung commented on 2021-07-26 04:23 (UTC) (edited on 2021-07-26 04:23 (UTC) by chenghung)

failed to run this application

$ sudo systemctl status portainer

portainer.service: Main process exited, code=exited, status=1/FAILURE

systemd[1]: portainer.service: Failed with result 'exit-code'.

bbrks commented on 2021-07-24 09:41 (UTC) (edited on 2021-07-24 09:41 (UTC) by bbrks)

@ng0177 make sure you've started (or permanently enabled) the service:

$ curl -I http://localhost:9000
curl: (7) Failed to connect to localhost port 9000: Connection refused

$ sudo systemctl status portainer
○ portainer.service - Portainer
     Loaded: loaded (/usr/lib/systemd/system/portainer.service; disabled; vendor preset: disabled)
     Active: inactive (dead)

$ sudo systemctl start portainer

$ sudo systemctl status portainer
● portainer.service - Portainer
     Loaded: loaded (/usr/lib/systemd/system/portainer.service; disabled; vendor preset: disabled)
     Active: active (running) since Sat 2021-07-24 10:38:58 BST; 2s ago
   Main PID: 14456 (portainer)
      Tasks: 20 (limit: 38429)
     Memory: 6.7M
        CPU: 81ms
     CGroup: /system.slice/portainer.service
             └─14456 /usr/bin/portainer --bind :9000 --data /var/lib/portainer --assets /usr/share/portainer

$ curl -I http://localhost:9000
HTTP/1.1 200 OK

Failing that, looking at the logs (journalctl -u portainer) might reveal why the service isn't starting correctly.

ng0177 commented on 2021-07-24 09:26 (UTC)

http://localhost:9000/ yields "This site can’t be reached"

kassane commented on 2021-06-03 14:02 (UTC) (edited on 2021-06-03 14:04 (UTC) by kassane)

@medicineman25 For that application to locate the directory /var/lib/portainer just modify the helper.go file of the mentioned project and compile.

bbrks commented on 2021-03-31 10:20 (UTC)

@angellusmortis I've got compose >3 support working as long as you have the optional docker-compose dependency installed.

Give it a try and let me know if you run into any issues!

medicineman25 commented on 2021-03-28 15:54 (UTC)

That worked. Thanks. Uninstalled package, deleted /var/lib/portainer, re-installed and restarted service. Option to set appeared.

bbrks commented on 2021-03-28 15:10 (UTC)

There isn't a default password. The first use after installation should guide you through creating an administrator account.

If this is not happening, I guess you've got a previous installation of Portainer? You can probably wipe existing data by removing the /var/lib/portainer directory.

medicineman25 commented on 2021-03-28 14:09 (UTC)

What is the default username and password? When starting the service it does not give an option to set.

Trying to reset via but it "cannot find /data/portainer.db on disk"

bbrks commented on 2021-03-21 22:46 (UTC)

It looks like I can might be able to get it working using the optional docker-compose package based on the changes in

Will take a look when I get a spare hour.

angellusmortis commented on 2021-03-21 17:54 (UTC)

Looks like latest build does not have Docker Compose v3 support for stack builds. Supported was added in this version (2.1.1) and the official Docker container has it, but it looks like this one still says only v2 is supported.

L0-FF commented on 2020-07-10 17:14 (UTC)

No worries,

Thanks for the update.


bbrks commented on 2020-07-10 09:39 (UTC)

Thanks L0-FF, I've updated the PKGBUILD with the correct checksum now. I've no idea how that happened.

L0-FF commented on 2020-07-10 04:13 (UTC)

Package does not install without updating SHA256 checksum of the portainer file (

Install with the: --editmenu option and update the chksum.