Docker Stacks

    Quote from Zoki

    ls -la like before

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

    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.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    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 think, yesterday you missed to change the docker root path when installing docker or had a type, That was the reason your stacks were done.


    Good you got it resolved.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    Quote from Zoki

    I think, yesterday you missed to change the docker root path when installing docker or had a type, That was the reason your stacks were done.


    Good you got it resolved.

    Well thanks to you for sticking with me and pointing me in a direction


    On a side note after the new reinstall, I cant access files through SMB/CIFS. Keep getting access denied. Is there a quick fix/check through CLI?


    I checked everything through the webUI and disabled/renabled SMB/CIFS. Also checked the permissions on shared folders (guests allowed).

    There is a ResetPerms plugin. If you recreated users they probably got differen ids in the new system, so ownership is changed.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

  • tannaroo

    Added the Label resolved
    • Official Post
    Quote from Zoki

    I think, yesterday you missed to change the docker root path when installing docker or had a type, That was the reason your stacks were done.


    Good you got it resolved.

    It appears that way.


    However if he has a data folder math for Portainer... He should be able to deploy those stacks on a completely new install whether his containers folder was backed up or not. I tested that in a virtual machine.

    I still dont understand why the portainer and docker path need to be in the same drive/location after a fresh install whereas my existing setup (pre-fresh install) they were in different locations and it was working fine.

    Quote from tannaroo

    I still dont understand why the portainer and docker path need to be in the same drive/location after a fresh install whereas my existing setup (pre-fresh install) they were in different locations and it was working fine.

    They don't have to.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    Quote from tannaroo

    but i'm just curious/trying to understand why the instructions were for installing portainer via CLI/docker-compose.yml rather than through the dropdown menu in OMV webUI

    The difference is where portainer stores it's data. If installed via UI, it creates a volume managed by docker (files end up at <your_docker_root>/volumes/portainer_data which is not to be accessed by you. If you use docker-compose.yml, you can define where portainer will keep it's data and in the example given it is sored as ordinary files on your data disk. This way they do not get lost, if you have to reinstall docker.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

    Like 1

    After my fresh system did a reboot last night, I just noticed that portainer was not started.


    I tried to docker start portainer but all I get is:


    Code
    root@OMV:/srv/dev-disk-by-uuid-fc008cb9-1532-4231-a49e-88721f97ba63/AppData2/portainer# sudo docker start portainer
Error response from daemon: get portainer_data: no such volume
Error: failed to start containers: portainer
    • Official Post
    Quote from tannaroo

    After my fresh system did a reboot last night, I just noticed that portainer was not started.


    I tried to docker start portainer but all I get is:


    Code
    root@OMV:/srv/dev-disk-by-uuid-fc008cb9-1532-4231-a49e-88721f97ba63/AppData2/portainer# sudo docker start portainer
Error response from daemon: get portainer_data: no such volume
Error: failed to start containers: portainer

    I guess the obvious question is the volume where you have portainer_data mapped, mounted.

    • Official Post
    Quote from tannaroo

    It is mounted and mapped.


    My docker-compose file /data is mapped as follows: - /srv/dev-disk-by-uuid-fc008cb9-1532-4231-a49e-88721f97ba63/AppData2/portainer:/data

    Obviously that doesn't make sense... are any other containers using that AppData2 path, and throwing any similar problems?


    Maybe try restarting the docker service and see if docker started before it mounted (although I thought Aaron fixed that)..


    Code
    systemctl restart docker    

    Give it a minute to start then see if portainer is still throwing that error.

    ok that worked - thanks


    my appdata2 folder also contains my docker storage path. so both docker and portainer are in the same folder. so this is likely to be a recurring issue as I guess portainer is conflicting before docker is running?

    You should not need to use docker start at all if you used docker-compose to create the stack. Always use docker-compose up in the directory containing the docker-compose.yml file.


    If you are using the docker-compose.yml KM0201 posted, there is restart: unless-stopped, so the docker daemon will restart portainer every time it starts up.


    Reboot yor system and check if docker and portainer are up. If not post the output of


    docker ps -a


    This has to be fixed.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login