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.026832
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 »

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.

https://docs.portainer.io/v/ce-2.11/advanced/cli#configuration-flags-available-at-the-command-line

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.

e.g.

[Service]
Environment="BIND=:9123"

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.

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