Package Details: portainer-bin 2:2.21.5-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
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: 14
Popularity: 0.000405
First Submitted: 2020-03-08 04:00 (UTC)
Last Updated: 2024-12-20 01:45 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

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!

« First ‹ Previous 1 2 3 4 5 Next › Last »