Posts by tannaroo

Quote from Zoki

What do you mean with "a complete fresh install" and "my stacks were there"? Isn't that contradicting eachother?

THe only Idea is, ypu have your docker root directory shifted to somewhere and this storage is not fully ok.

Meaning I completely wiped my system drive and reinstalled OMV from the start.

When I got to installing portainer, I followed post #2 and #36. That is ensuring that my docker and portainer were in the same drive/location.

Docker = /srv/dev-disk-by-uuid-fc008cb9-1532-4231-a49e-88721f97ba63/AppData2/Docker

Portainer = /srv/dev-disk-by-uuid-fc008cb9-1532-4231-a49e-88721f97ba63/AppData2/Portainer

I realised today that yesterday's install - Docker and Portainer were not in the same drive/location. Not sure if this makes the difference. But when I got to Portainer, my original stacks were there. I tried restarting them but got errors.

But I deleted the old stacks and just tried a new stack and SUCCESS.

I've done yet another fresh complete install. Went into my portainer - this time all of my stacks were there.

I tried to deploy a couple of them but still get the same timeout error, wont deploy

sigh...

Quote from Zoki

ls -la like before

root@OMV:/srv/dev-disk-by-uuid-402ee138-65a8-442a-83d7-407c5861dc43/AppData# ls -la
total 32
drwxrwsrwx+ 8 root users 4096 Jan 31 17:00 .
drwxr-xr-x  9 root root  4096 Jan 29 21:13 ..
drwxrwsrwx+ 6 rob  users 4096 Jun 10  2020 LMS
drwxrwsrwx+ 3 root users 4096 Jun  1  2020 pihole
drwxr-xr-x  7 root users 4096 Jan 31 17:02 portainer
drwxrwsrwx+ 4 root users 4096 Jul 16  2020 Resilio
drwxr-sr-x+ 3 root root  4096 Nov 16 14:28 syncthing
drwxrwsrwx+ 4 rob  users 4096 Jan 28 03:34 urbackup
root@OMV:/srv/dev-disk-by-uuid-402ee138-65a8-442a-83d7-407c5861dc43/AppData# cd portainer
root@OMV:/srv/dev-disk-by-uuid-402ee138-65a8-442a-83d7-407c5861dc43/AppData/portainer# ls -la
total 104
drwxr-xr-x  7 root users  4096 Jan 31 17:02 .
drwxrwsrwx+ 8 root users  4096 Jan 31 17:00 ..
drwx------  2 root root   4096 Jan 31 17:02 bin
drwx------  2 root root   4096 Jan 31 17:02 certs
drwx------  2 root root   4096 Jan 31 17:08 compose
-rwxr-xr-x  1 root users   379 Jan 31 16:59 docker-compose.yml
drwx------  2 root root   4096 Jan 31 17:08 docker_config
-rw-------  1 root root  65536 Jan 31 17:07 portainer.db
-rw-------  1 root root    227 Jan 31 17:02 portainer.key
-rw-------  1 root root    190 Jan 31 17:02 portainer.pub
drwx------  2 root root   4096 Jan 31 17:02 tls
root@OMV:/srv/dev-disk-by-uuid-402ee138-65a8-442a-83d7-407c5861dc43/AppData/portainer#

Quote from Zoki

Did you check, the ACLs and the SGID bit are unset?

Never surrender

Not sure how to do that.

I've been on this for 3 days solid. As you know (and helped me) my original OMV had a hard drive failure, so had to deal with that.

I just need a break from this, so maybe I will be back tomorrow.

Quote from Zoki

You are right, i usually place my docker-compose.yml inside a directory i use for the config data of the container. if you need help, just post.

Well I have followed the steps carefully and done this twice (i.e. removed portainer, reset permissions/ re-install). But on both occasions when I go into portainer to setup one or two of my stacks....same problem as before.

i think we have to admit defeat.

Quote from Zoki

OK, permissions are messed up, start all over, one command at a time.

Code

/srv/dev-disk-by-uuid-402ee138-65a8-442a-83d7-407c5861dc43/AppData/portainer
docker-compose down            # stop portainer
cp docker-compos.yml ..        # make a backup copy of the stack
cd ..                          # one directory up
rm -rf portaner                # remove old portainer directory
mkdir portainer                # start over with fresh directory
mv docker-compoy.yml portainer # and copy of the compose file
chmod -R 755 portainer         # reset permissions
chmod -R g-s portainer         # still reset permissions
setfacl -R -b portainer        # and remove ACLs
cd portainer                   # now we schould be ready for the next try
docker-compose up -d           # if this works, be happy

Display More

ok really appreciate the help!

step 1 - i presume you meant cd then the directory to stop portainer but when i try to stop portainer (step 2) i get an error it can't find the docker-compose.yml file. This is because in #2, the instructions were to set up a new directory /portainer which maybe where the error has occurred. This directory happened from my root. So think I get the gist of your approach. The mkdir portainer should happen on the external drive

Quote from Zoki

So the situation is, you can create a "stack" from a docker-compose.yml, but not from the sae definition inside portainer.

Is this understanding correct?

Second: You did create a new directory for portainer when creating it from docker-compose.yml

Can you show me the permissions auf the directories AppData and AppData/portainer and the contents of AppData/portainer.

Use ls -la and paste inside a code box please (notinline code)

Display More

Well I have not tried creating stacks (other than portainer) from docker-compose.yml but yes I cannot create any stacks from inside portainer, which is what I normally/can do.

root@OMV:~# cd /srv/dev-disk-by-uuid-402ee138-65a8-442a-83d7-407c5861dc43/AppData
root@OMV:/srv/dev-disk-by-uuid-402ee138-65a8-442a-83d7-407c5861dc43/AppData# ls -la
total 32
drwxrwsrwx+ 8 root users 4096 Jan 30 18:36 .
drwxr-xr-x  9 root root  4096 Jan 29 21:13 ..
drwxrwsrwx+ 6 rob  users 4096 Jun 10  2020 LMS
drwxrwsrwx+ 3 root users 4096 Jun  1  2020 pihole
drwxr-sr-x+ 7 root root  4096 Jan 30 18:36 portainer
drwxrwsrwx+ 4 root users 4096 Jul 16  2020 Resilio
drwxr-sr-x+ 3 root root  4096 Nov 16 14:28 syncthing
drwxrwsrwx+ 4 rob  users 4096 Jan 28 03:34 urbackup

root@OMV:/srv/dev-disk-by-uuid-402ee138-65a8-442a-83d7-407c5861dc43/AppData/portainer# ls -la
total 124
drwxr-sr-x+ 7 root root   4096 Jan 30 18:36 .
drwxrwsrwx+ 8 root users  4096 Jan 30 18:36 ..
drwx--S---+ 2 root root   4096 Jan 30 18:36 bin
drwx--S---+ 2 root root   4096 Jan 30 18:36 certs
drwx--S---+ 3 root root   4096 Jan 31 15:42 compose
drwx--S---+ 2 root root   4096 Jan 31 14:35 docker_config
-rw-------+ 1 root root  86016 Jan 31 16:05 portainer.db
-rw-------+ 1 root root    227 Jan 30 18:36 portainer.key
-rw-------+ 1 root root    190 Jan 30 18:36 portainer.pub
drwx--S---+ 2 root root   4096 Jan 30 18:36 tls

Quote from Zoki

I just started the portainer docker-compose posted earlier in this thread:

What do you have in the yellow spot?

I have the same. /var/run/docker.sock

On the admin password, if referring to when I first open portainer, I did create a password for admin

Quote from Zoki

I did not see that while posting. Have you configured portainer after installing it with the docker-compose.yml?

it lloks like portainer is not configured to talk to you local docker daemon and has no admin credentials.

After my OMV re-installation due to system drive failure, I installed Portainer through the OMV web UI but was told not to do that. So I removed it and followed the instructions on post #2.

It seems since my first OMV / Portainer installation a couple of years ago, things have changed so it seems there are further steps required?

Quote from Zoki

To be honest, I can not make sense of the error message. The resilio image is not on the server, but it is starting up ???

Is portainer talking to the local docker daemon? Let's see

Did the error message from #25 help to diagnose the problem?

Though I initially installed Portainer through the web interface but was told to remove it and go through CLI. So my docker compose in in cd portainer

root@OMV:~/portainer# docker-compose up

Building with native build. Learn about native build in Compose here: https://docs.docker.com/go/compose-native-build/

portainer is up-to-date

Attaching to portainer

portainer | level=info msg="2022/01/30 18:36:15 [INFO] [internal,ssl] [message: no cert files found, generating self signed ssl certificates]"

portainer | 2022/01/30 18:36:15 server: Reverse tunnelling enabled

portainer | 2022/01/30 18:36:15 server: Fingerprint 0a:d0:93:5b:92:8b:e0:2b:37:b3:7c:67:71:47:6a:db

portainer | 2022/01/30 18:36:15 server: Listening on 0.0.0.0:8000...

portainer | level=info msg="2022/01/30 18:36:15 [INFO] [cmd,main] Starting Portainer version 2.11.0"

portainer | level=info msg="2022/01/30 18:36:15 [DEBUG] [chisel, monitoring] [check_interval_seconds: 10.000000] [message: starting tunnel management process]"

portainer | level=info msg="2022/01/30 18:36:15 [DEBUG] [internal,init] [message: start initialization monitor ]"

portainer | level=info msg="2022/01/30 18:36:15 [INFO] [http,server] [message: starting HTTPS server on port :9443]"

portainer | level=info msg="2022/01/30 18:36:15 [INFO] [http,server] [message: starting HTTP server on port :9000]"

portainer | level=info msg="2022/01/30 18:37:02 http error: A valid authorisation token is missing (err=Unauthorized) (code=401)"

portainer | level=info msg="2022/01/30 18:37:02 http error: A valid authorisation token is missing (err=Unauthorized) (code=401)"

portainer | level=info msg="2022/01/30 18:37:02 http error: A valid authorisation token is missing (err=Unauthorized) (code=401)"

portainer | level=info msg="2022/01/30 18:37:02 http error: No administrator account found inside the database (err=Object not found inside the database) (code=404)"

portainer | level=info msg="2022/01/30 18:37:02 http error: No administrator account found inside the database (err=Object not found inside the database) (code=404)"

portainer | level=info msg="2022/01/30 18:37:02 http error: No administrator account found inside the database (err=Object not found inside the database) (code=404)"

portainer | level=info msg="2022/01/30 18:37:16 http error: Unable to initiate communications with environment (err=unable to load in-cluster configuration, KUBERNETES_SERVICE_HOST and KUBERNETES_SERVICE_PORT must be defined) (code=500)"

portainer | level=info msg="2022/01/30 18:42:30 http error: failed to deploy a stack: Pulling resilio-sync (lscr.io/linuxserver/resilio-sync:)..."

portainer | level=info msg="Creating resilio-sync ... "

portainer | level=info

portainer | level=info msg="ERROR: for resilio-sync UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"

portainer | level=info

portainer | level=info msg="ERROR: for resilio-sync UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"

portainer | level=info msg="An HTTP request took too long to complete. Retry with --verbose to obtain debug information."

portainer | 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)."

portainer | level=info msg=": exit status 1 (err=failed to deploy a stack: Pulling resilio-sync (lscr.io/linuxserver/resilio-sync:)..."

portainer | level=info msg="Creating resilio-sync ... "

portainer | level=info

portainer | level=info msg="ERROR: for resilio-sync UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"

portainer | level=info

portainer | level=info msg="ERROR: for resilio-sync UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"

portainer | level=info msg="An HTTP request took too long to complete. Retry with --verbose to obtain debug information."

portainer | 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)."

portainer | level=info msg=": exit status 1) (code=500)"

portainer | level=info msg="2022/01/30 18:46:38 http error: failed to deploy a stack: Pulling resilio-sync (lscr.io/linuxserver/resilio-sync:)..."

portainer | level=info msg="Recreating resilio-sync ... "

portainer | level=info

portainer | level=info msg="ERROR: for resilio-sync UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"

portainer | level=info

portainer | level=info msg="ERROR: for resilio-sync UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"

portainer | level=info msg="An HTTP request took too long to complete. Retry with --verbose to obtain debug information."

portainer | 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)."

portainer | level=info msg=": exit status 1 (err=failed to deploy a stack: Pulling resilio-sync (lscr.io/linuxserver/resilio-sync:)..."

portainer | level=info msg="Recreating resilio-sync ... "

portainer | level=info

portainer | level=info msg="ERROR: for resilio-sync UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"

portainer | level=info

portainer | level=info msg="ERROR: for resilio-sync UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"

portainer | level=info msg="An HTTP request took too long to complete. Retry with --verbose to obtain debug information."

portainer | 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)."

portainer | level=info msg=": exit status 1) (code=500)"

portainer | level=info msg="2022/01/30 19:36:24 http error: failed to deploy a stack: Pulling lms (dlandon/logitechmediaserver:)..."

portainer | level=info msg="Creating lms ... "

portainer | level=info

portainer | level=info msg="ERROR: for lms UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"

portainer | level=info

portainer | level=info msg="ERROR: for lms UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"

portainer | level=info msg="An HTTP request took too long to complete. Retry with --verbose to obtain debug information."

portainer | 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)."

portainer | level=info msg=": exit status 1 (err=failed to deploy a stack: Pulling lms (dlandon/logitechmediaserver:)..."

portainer | level=info msg="Creating lms ... "

portainer | level=info

portainer | level=info msg="ERROR: for lms UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"

portainer | level=info

portainer | level=info msg="ERROR: for lms UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)"

portainer | level=info msg="An HTTP request took too long to complete. Retry with --verbose to obtain debug information."

portainer | 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)."

portainer | level=info msg=": exit status 1) (code=500)"

portainer | level=info msg="2022/01/30 20:19:26 http error: failed to deploy a stack: Pulling urbackup (morlan/urbackup_docker:latest)..."

portainer | level=info msg="The image for the service you're trying to recreate has been removed. If you continue, volume data could be lost. Consider backing up your data before continuing."

portainer | level=info

portainer | level=info msg="pull access denied for morlan/urbackup_docker, repository does not exist or may require 'docker login': denied: requested access to the resource is denied"

portainer | level=info msg=": exit status 1 (err=failed to deploy a stack: Pulling urbackup (morlan/urbackup_docker:latest)..."

portainer | level=info msg="The image for the service you're trying to recreate has been removed. If you continue, volume data could be lost. Consider backing up your data before continuing."

portainer | level=info

portainer | level=info msg="pull access denied for morlan/urbackup_docker, repository does not exist or may require 'docker login': denied: requested access to the resource is denied"

portainer | level=info msg=": exit status 1) (code=500)"

Quote from Zoki

Assuming the helloworld image has not been on your computer befor pulling and starting containers works.

Next step:

docker image ls

create a new directory somewhere and cd to it

create a file docker-compose.yml and paste one of the stack which do not start into it

docker-compose up and paste the output into a code box </> in the editor bar, easier to read than the inlie command.

Display More

root@OMV:~# docker image ls

REPOSITORY TAG IMAGE ID CREATED SIZE

dlandon/logitechmediaserver latest 53a4242e55d1 4 weeks ago 1.38GB

portainer/portainer-ce latest 0df02179156a 7 weeks ago 273MB

hello-world latest feb5d9fea6a5 4 months ago 13.3kB

Looks like this is the problem?

root@OMV:~# docker-compose up

ERROR:

Can't find a suitable configuration file in this directory or any

parent. Are you in the right directory?

Supported filenames: docker-compose.yml, docker-compose.yaml

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/

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

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

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

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

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?

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:)..."

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

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.

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.