Posts by Nitrousoxide

  • omv-extras 6.3 / openmediavault-compose 6.7

    Heh, you could convert that to a docker-compose file too I suppose and ssh into omv and just do


    Code
    docker-compose up

    For me, since I just have that command in a Joplin note it's trivial to paste it into an ssh session to redeploy Portainer when an update is available. Portainer is the only thing I deploy with docker run, however. Everything else is stacks (docker-compose).


    Personally, I'm thinking about transitioning to Podman, but that'd require switching out of OMV since the Podman version here is so ancient (3.0.1 vs the modern 4.5.0)

  • omv-extras 6.3 / openmediavault-compose 6.7

    I just want to point out that this change does very little to stop you from continuing to use portainer for as long as you want. Portainer is just a docker container with the docker.sock mounted to it as a volume claim. You can just do a docker run command to spin it up any time you want.

    I use this (I tweaked the ports slightly for my setup_:

    Code
    docker run --pull=always -d -p 8001:8000 -p 9001:9000 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest


    The only difference is needing to ssh into your omv server to stop, rm, and re-run the command when there's a portainer update rather than having a one click button to redeploy.

  • docker not working since omv-upgrade

    Portainer doesn't seem to install/start even with that workaround (though the rest of the containers do)


    Edit: I SSH'd into the server and tried to create portainer there. I got this error:


    Code
    $ docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ee:latest
049dfdf8d2d99f945f56b76cd7ce15b8626acfd41049b790bb240d97ed41118b
docker: Error response from daemon: driver failed programming external connectivity on endpoint portainer (4037a0761505758b37c5d8dbb71d4e2f5e0c047ec297531b9cf73e3fe0ee80e2): Error starting userland proxy: listen tcp4 0.0.0.0:8000: bind: address already in use.


    moving the portainer ports to 9001 and 8001 seems to have fixed it. It looks like something new is listening in on port 8000 now. I've not changed any other containers and none of them should have been listening in on port 8000


    Code
    $ sudo lsof -i tcp:8000
COMMAND    PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
homebridg 9756 root   31u  IPv6  86583      0t0  TCP *:8000 (LISTEN)

    Edit edit: Looks like homebridge was the culperate (it needs netadmin to run correctly and that apparently means it's listening in on port 8000). Maybe something related to the docker patch. I don't know. I guess there's not really much OMV can/should do about that other than maybe switching the default portainer ports. But I suppose that's an OMV Extra change request not OMV itself.