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 MoreAssuming 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.
That's what is weird, he got portainer to install via docker-compose...
I'm wondering if it's a permission issue on one of those the /data folder.
Display MoreAssuming 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.
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
Did you create the docker-compose.yml file in the directory? It only say, it does not know what to start.
That's what is weird, he got portainer to install via docker-compose...
I'm wondering if it's a permission issue on one of those the /data folder.
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
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?
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.
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?
Set the admin password
Define the docker host (local) to talk to.
I do not see, how you could do without that.
I just started the portainer docker-compose posted earlier in this thread:
What do you have in the yellow spot?
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
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 MoreSo 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)
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 urbackuproot@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 tlsOK, permissions are messed up, start all over, one command at a time.
/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 happyOK, permissions are messed up, start all over, one command at a time.
CodeDisplay More/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
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
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.
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.
Did you check, the ACLs and the SGID bit are unset?
Never surrender
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.
Don’t have an account yet? Register yourself now and be a part of our community!
