Docker Stacks

tannaroo · Jan 30th 2022

I've had to re-install OMV. Tring to redeploy my saved stacks but none of them are working. Has the way stacks are deployed in Portainer changed recently?

KM0201 · Jan 30th 2022

Quote from tannaroo

I've had to re-install OMV. Tring to redeploy my saved stacks but none of them are working. Has the way stacks are deployed in Portainer changed recently?

You probably didn't have portainer mapped to a /data directory. This is where that stuff is saved. I'm guessing in Portainer under stacks it shows them as "limited" control (or something like that.. ).. rather than "full"

Easiest way to do this is to install portainer with docker-compose (it's to late for you now, but for future reference)

mkdir portainer

cd portainer

nano docker-compose.yml

copy-paste the below, and adjust your volume mapping for /data

Code

version: "2.2"
services:
  portainer:
    image: portainer/portainer-ce:latest
    container_name: portainer
    volumes:
      - /NAS/AppData/portainer:/data
      - /var/run/docker.sock:/var/run/docker.sock
      - /etc/localtime:/etc/localtime:ro
    ports:
      - 8000:8000
      - 9000:9000
    restart: unless-stopped

Display More

Cntrl X, then Y, then Enter to save

Back at the prompt

Code

docker-compose up -d

If you ever have to reinstall.. make sure that data folder is backed up, reinstall, and then install Portainer with docker-compose and make sure it's pointed at that data volume... All your stacks will be there and can be easily edited or redeployed.

tannaroo · Jan 30th 2022

ok thanks. and should the path to drive now be done by uuid as I believe disk by label was removed?

KM0201 · Jan 30th 2022

Quote from tannaroo

ok thanks. and should the path to drive now be done by uuid as I believe disk by label was removed?

Assuming you dont have labels and have uuid, yes

tannaroo · Jan 30th 2022

I've done all that but I still cant get the stacks working. Just got a long red box message something about the container is already in use but its not installed.

KM0201 · Jan 30th 2022

Quote from tannaroo

I've done all that but I still cant get the stacks working. Just got a long red box message something about the container is already in use but its not installed.

I told you it's not going to help you at this point.. because you didn't have it set up that way before you reinstalled. If you're trying to set this up in anticipation of the next time this happens.. You need to uninstall Portainer (however you installed it before).. or use Portainer to delete the portainer container (you can do that)..

Then run the docker-compose.

tannaroo · Jan 30th 2022

Ok. I don't know what I am doing. And I am giving up with this. I just dont have the patience anymore.

For me, I always run into problems and yes it is probably 99% the user.

KM0201 · Jan 30th 2022

Quote from tannaroo

Ok. I don't know what I am doing. And I am giving up with this. I just dont have the patience anymore.

For me, I always run into problems and yes it is probably 99% the user.

What are you having problems with?

tannaroo · Jan 30th 2022

portainer has been uninstalled/removed from omv web gui.

setup docker compose with mapped data drive per post #2

ran docker-compose up -d

logged into portainer ui

tried to deploy one of my stacks - didn't work.

edit: log says No log line matching the '' filter

KM0201 · Jan 30th 2022

Quote from tannaroo

portainer has been uninstalled/removed from omv web gui.
setup docker compose with mapped data drive per post #2
ran docker-compose up -d
logged into portainer ui
tried to deploy one of my stacks - didn't work.
edit: log says No log line matching the '' filter

Display More

Never seen that one.

Did you try a second one to see if maybe it was just something wrong with that stack?

tannaroo · Jan 30th 2022

Quote from KM0201

Never seen that one.

Did you try a second one to see if maybe it was just something wrong with that stack?

Yes tried all of them.

This is a further log for resilio. Looks like some connection issue?

Code

level=info msg="Creating resilio-sync ... "
level=info
level=info msg="ERROR: for resilio-sync  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"
level=info
level=info msg="ERROR: for resilio-sync  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"
level=info msg="An HTTP request took too long to complete. Retry with --verbose to obtain debug information."
level=info msg="If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60)."
level=info msg=": exit status 1) (code=500)"
level=info msg="2022/01/30 18:46:38 http error: failed to deploy a stack: Pulling resilio-sync (lscr.io/linuxserver/resilio-sync:)..."
level=info msg="Recreating resilio-sync ... "
level=info
level=info msg="ERROR: for resilio-sync  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"
level=info
level=info msg="ERROR: for resilio-sync  UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"
level=info msg="An HTTP request took too long to complete. Retry with --verbose to obtain debug information."
level=info msg="If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60)."
level=info msg=": exit status 1 (err=failed to deploy a stack: Pulling resilio-sync (lscr.io/linuxserver/resilio-sync:)..."

Display More

KM0201 · Jan 30th 2022

Is your server online?

What is the output of

Code

ping -c5 google.com

It looks like it might be a DNS error.

tannaroo · Jan 30th 2022

Quote from KM0201
Is your server online?

What is the output of
Code
ping -c5 google.com
It looks like it might be a DNS error.

Its online and receiving data

Code

root@OMV:~# ping -c5 google.com
PING google.com (142.250.179.238) 56(84) bytes of data.
64 bytes from lhr25s31-in-f14.1e100.net (142.250.179.238): icmp_seq=1 ttl=119 time=13.2 ms
64 bytes from lhr25s31-in-f14.1e100.net (142.250.179.238): icmp_seq=2 ttl=119 time=13.5 ms
64 bytes from lhr25s31-in-f14.1e100.net (142.250.179.238): icmp_seq=3 ttl=119 time=13.1 ms
64 bytes from lhr25s31-in-f14.1e100.net (142.250.179.238): icmp_seq=4 ttl=119 time=13.2 ms
64 bytes from lhr25s31-in-f14.1e100.net (142.250.179.238): icmp_seq=5 ttl=119 time=12.9 ms

--- google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 8ms
rtt min/avg/max/mdev = 12.895/13.161/13.451/0.234 ms

Display More

KM0201 · Jan 30th 2022

Quote from tannaroo

Its online and receiving data

Code

root@OMV:~# ping -c5 google.com
PING google.com (142.250.179.238) 56(84) bytes of data.
64 bytes from lhr25s31-in-f14.1e100.net (142.250.179.238): icmp_seq=1 ttl=119 time=13.2 ms
64 bytes from lhr25s31-in-f14.1e100.net (142.250.179.238): icmp_seq=2 ttl=119 time=13.5 ms
64 bytes from lhr25s31-in-f14.1e100.net (142.250.179.238): icmp_seq=3 ttl=119 time=13.1 ms
64 bytes from lhr25s31-in-f14.1e100.net (142.250.179.238): icmp_seq=4 ttl=119 time=13.2 ms
64 bytes from lhr25s31-in-f14.1e100.net (142.250.179.238): icmp_seq=5 ttl=119 time=12.9 ms

--- google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 8ms
rtt min/avg/max/mdev = 12.895/13.161/13.451/0.234 ms

Display More

Nevermind.. definitely not that.

It's complaining about a connection problem though from the log.. weird.

tannaroo · Jan 30th 2022

would this have anything to do with iptables (legacy vs nft)

KM0201 · Jan 30th 2022

Quote from tannaroo

would this have anything to do with iptables (legacy vs nft)

I don't use IPtables, but I would assume it could.

tannaroo · Jan 30th 2022

i dont as well but I did accidently use the drop down menu 'use legacy'

Zoki · Jan 30th 2022

Before you give up. lets try to figure out wht the problem really is: from the cli:

docker ps -a

docker volume ls

docker run hello-world

Post the output of each of these commands.

tannaroo · Jan 30th 2022

root@OMV:~# docker ps -a

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

75b269ea6a79 dlandon/logitechmediaserver "/sbin/my_init" 28 minutes ago Created lms

ae6545936d5e portainer/portainer-ce:latest "/portainer" About an hour a go Up About an hour 0.0.0.0:8000->8000/tcp, :::8000->8000/tcp, 9443/tcp, 0.0 .0.0:9200->9000/tcp, :::9200->9000/tcp portainer

root@OMV:~# docker volume ls

DRIVER VOLUME NAME

local 7a5250ccf928a4208e5c34c4f9dd368121e202e6d6510a0084f0dd8317d6ba27

local 90a98d50365e43420f8b723ca37012ab732c315c8ea547138677321556a8e7b5

local portainer_data

root@OMV:~# docker run hello-world

Unable to find image 'hello-world:latest' locally

latest: Pulling from library/hello-world

2db29710123e: Pull complete

Digest: sha256:507ecde44b8eb741278274653120c2bf793b174c06ff4eaa672b713b3263477b

Status: Downloaded newer image for hello-world:latest

Hello from Docker!

This message shows that your installation appears to be working correctly.

To generate this message, Docker took the following steps:

1. The Docker client contacted the Docker daemon.

2. The Docker daemon pulled the "hello-world" image from the Docker Hub.

(amd64)

3. The Docker daemon created a new container from that image which runs the

executable that produces the output you are currently reading.

4. The Docker daemon streamed that output to the Docker client, which sent it

to your terminal.

To try something more ambitious, you can run an Ubuntu container with:

$ docker run -it ubuntu bash

Share images, automate workflows, and more with a free Docker ID:

https://hub.docker.com/

For more examples and ideas, visit:

https://docs.docker.com/get-started/

KM0201 · Jan 30th 2022

So docker works (always forget about hello docker)

Docker Stacks

Participate now!

Similar Threads

Portainer Error

docker and portainer ip question

Issues launching docker containers after upgrading to 5

portainer lost stack/ compose

Dell workstation -> server