Package Details: portainer-bin 2:2.20.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
Upstream URL: https://github.com/portainer/portainer
Keywords: docker management monitoring webui
Licenses: custom:zlib
Conflicts: portainer
Provides: portainer
Submitter: bbrks
Maintainer: bbrks
Last Packager: bbrks
Votes: 14
Popularity: 0.000596
First Submitted: 2020-03-08 04:00 (UTC)
Last Updated: 2024-03-20 21:09 (UTC)

Latest Comments

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

Turtizzle commented on 2022-11-10 12:44 (UTC) (edited on 2022-11-11 12:50 (UTC) by Turtizzle)

Oh my god. I could have guessed that based on the portainer.service file in the sources... it never even crossed my mind. Thank you very much!

bbrks commented on 2022-11-09 15:56 (UTC)

@Turtizzle this application is designed to run as a systemd service

You can start it using

sudo systemctl start portainer

If you really want to run it from the command line, you will need to provide additional arguments like the service script does. E.g.

portainer --data /var/lib/portainer --assets /usr/share/portainer

Turtizzle commented on 2022-11-09 15:15 (UTC) (edited on 2022-11-09 15:15 (UTC) by Turtizzle)

I get a "404 page not found" when trying to access localhost:9000 after starting portainer. I do not understand what's causing the error - running docker images in terminal works fine.

alex@iris ~ % sudo portainer
[sudo] Passwort für alex:
2022/11/09 04:03PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:530 > encryption key file not present | filename=portainer
2022/11/09 04:03PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:549 > proceeding without encryption key |
2022/11/09 04:03PM INF github.com/portainer/portainer/api/database/boltdb/db.go:124 > loading PortainerDB | filename=portainer.db
2022/11/09 16:03:03 server: Reverse tunnelling enabled
2022/11/09 16:03:03 server: Fingerprint 7c:31:d9:7f:99:fe:dd:0e:45:9c:a2:5b:98:08:2c:dd
2022/11/09 16:03:03 server: Listening on 0.0.0.0:8000...
2022/11/09 04:03PM INF github.com/portainer/portainer/api/cmd/portainer/main.go:789 > starting Portainer | build_number=24941 go_version=1.19.3 image_tag=linux-amd64-2.16.1 nodejs_version=18.12.1 version=2.16.1 webpack_version=5.68.0 yarn_version=1.22.19
2022/11/09 04:03PM INF github.com/portainer/portainer/api/http/server.go:337 > starting HTTPS server | bind_address=:9443
2022/11/09 04:03PM INF github.com/portainer/portainer/api/http/server.go:322 > starting HTTP server | bind_address=:9000

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

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