Posts by Mr.Onion

    You need to make a folder, that is at the top of the directory (ie, right under the UUID) and set that to be where you store containers.

    I thought that was what I had done, but on closer inspection I see that wasn't the case at all... I think I'll start over with a new installation of omv and do better this time. Just so I understand you correctly: this folder is what I should specify under "Docker storage" when installing docker in the omv gui?

    777 really shouldn't be your answer either... learn to properly set your permissions.

    Couldnt agree more... Fail and learn, I suppose!

    Thank you all for taking the time to reply!


    Regarding the updating of nextcloud (maybe not relevant in this forum, I apologize in that case):

    Cicking the update now-button in the gui just returns me to the dashboard page, and after a bit of googling I found this post leading me to this part of the nextcloud docker github page stating that upgrading is done by pulling the new image.


    It's somewhat of a moot point for me right now, though, because I seem to have messed something up when fiddling around with permissions (and being really stupid and mixing up chmod and chown, among other dumb stuff) and now nginx isn't working and I'm thinking that a fresh install actually might be faster and more fun than untangling the mess I've made of this.


    Something that's been happening that I would love to get some thoughts on, before marking the thread as solved, is that it turns out that the drive (/srv/dev-disk-by-[stuff]) that has my Docker share has different permissions than the other drives I have connected (/srv/dev-disk-by[other stuff x2]).

    ls -ld /srv/dev-disk-by-[other stuff x2] (my other two drives)

    gives me

    drwxrwxrwx 4 root root 4096

    but

    ls -ld /srv/dev-disk-by-[stuff] (the drive that houses docker)

    returns

    drwx--x--- 20 root root 4096


    I've changed the permissions to 777

    sudo su (because sudo chmod doesn't seem to do anything)

    chmod 777 /srv/dev-disk-by-[stuff]

    but the permissions turn back to 710 after a while and I don't know why...

    Subfolders have varied permissions that seem to reflect acl settings done in omv gui.

    Hello!


    I have a problem that might be a symptom of another problem, so please bear with my rambling question...


    My RPi4 is running omv 6 (I can't remember if it's a clean install or if I upgraded from 5 at any point), and I have Nextcloud (together with nginx and some other images) running on docker. I can't really remember what guide I used to install and setup (dbtech's video guides mostly), but it's been working well (as far as I can tell) for months now.


    Now there's an update for Nextcloud, and I would like to upgrade to it. Other containers I successfully "recreate" in portainer, which pulls the latest image. When I try to do the same with the Nextcloud app (nextcloud_app_1) I get the error "Failure pull access denied for sha256, repository does not exist or may require 'docker login': denied: requested access to the resource is denied", and the same happens with Nextcloud's database (nextcloud_db_1).


    I would like to try docker-compose pull, but when I login via ssh I cannot access the drive (and the subsequent share) that Docker is installed on, despite setting file and folder permissions to allow that in as many ways as I could think of, without them giving me errors. File permissions make my head hurt, and I can't say that I understand them in any meaningful way when it comes to troubleshooting, so there might be something really simple that I'm missing. My other drives I can cd to without issues, but the one with Docker on gives me "Permission denied".


    Everything looks healthy enough in the omv gui and in portainer, as far as I can see, but obviously something isn't working as it should and I can't really think of anything else to try, and googling hasn't lead me to find anything helpful.

    Oh, no, I'm too stupid...
    I was trying to access the web interface at the wrong ip-adress, and when that didn't work I checked the logs and thought that the first line ([s6-init] making user provided files available at /var/run/s6/etc...exited 0.) was the last line and an error message about permissions.
    Anyway, it's been working all this time, and I'm very grateful for the time you wasted on me!

    Oh, sorry, my bad!


    Here it is:


    root@raspberrypi:/srv/dev-disk-by-label-Hubbn# ls -al
    total 74484
    drwxrwxrwx 15 root root 4096 Jan 8 19:38 .
    drwxr-xr-x 7 root root 4096 Dec 17 20:38 ..
    drwxrwsrw-+ 46 root users 12288 Feb 7 2017 Barnfilm
    drwx------ 4 root root 4096 Apr 25 2016 'Bilder som ingen någonsin kommer orka rensa i'
    -rw-rw-rw- 1 root root 15724454 Oct 9 2016 CPbackup
    drwxrwx--x+ 3 docker users 4096 Jan 8 19:13 Docker
    drwxrwsr-x+ 2 docker users 4096 Jan 8 19:41 Docker2
    drwxrwsrwx+ 9 docker users 4096 Jan 8 19:34 Downloads
    drwxrwsr-x+ 9 root users 4096 Sep 18 2017 Emulation
    drwxrws---+ 229 root users 16384 Jun 16 2018 Musik
    drwxrws---+ 3 root users 4096 Oct 14 2016 Musikfilm
    drwxrwsr-x+ 5 docker users 4096 Jan 8 19:25 NZBGet
    drwx--S--- 6 root users 4096 Dec 22 2011 Noter
    -rw-rw-rw- 1 root root 2467657 Jul 9 2016 SABbackup
    drwxrws---+ 11 root users 4096 Jan 8 19:34 Safe
    drwxrwsrw-+ 27 root users 4096 Nov 16 18:42 TV
    -rw------- 1 root root 57921087 Jul 12 2013 'Video 2013-07-09 12 30 12.mov'
    -rw------- 1 root root 9216 Dec 27 19:22 aquota.group
    -rw------- 1 root root 7168 Dec 27 19:22 aquota.user
    drwx------ 2 root root 16384 Apr 26 2016 lost+found

    /config points to /srv/dev-disk-by-label-Hubbn/Docker. Output of ls -al in that folder is in post number 6 above.


    /downloads points to /srv/dev-disk-by-label-Hubbn/Downloads. Output of ls -al in that folder follows here:


    root@raspberrypi:/srv/dev-disk-by-label-Hubbn/Downloads# ls -al
    total 1770908
    drwxrwsrwx+ 9 docker users 4096 Jan 8 19:34 .
    drwxrwxrwx 14 root root 4096 Jan 8 19:24 ..
    drwxrwsrwx+ 3 docker users 12288 Jul 11 2017 SAB
    drwxrwsrwx+ 3 docker users 4096 May 13 2018 docker
    drwxrwsrwx+ 3 docker users 4096 May 10 2018 home
    drwxrwsrwx+ 28 docker users 4096 Dec 2 23:12 intermediate
    drwxrwsrwx+ 2 docker users 32768 Dec 30 20:02 nzb
    -rwxrwxrwx+ 1 docker users 1812847329 Jan 8 19:25 nzbget.log
    drwxrwsrwx+ 2 docker users 266240 Dec 30 20:02 queue
    drwxrwsrwx+ 2 docker users 4096 Dec 2 22:59 tmp


    Please tell me if I'm using ls -al command incorrectly!


    I just realized I used both of these folders in the old installation, I'll just try once with clean newly created folders.

    Here it is:


    root@raspberrypi:/srv/dev-disk-by-label-Hubbn/Docker# ls -al
    total 2408
    drwxrwx--x+ 3 docker users 4096 Jan 8 18:13 .
    drwxrwxrwx 13 root root 4096 Oct 3 22:17 ..
    -rw-rw----+ 1 docker users 307 Jan 8 15:05 config.xml
    drwxrwx--x+ 2 docker users 4096 Jan 8 15:05 logs
    -rw-r-----+ 1 docker users 32768 Jan 8 18:13 logs.db
    -rw-r-----+ 1 docker users 299008 Jan 8 16:58 nzbdrone.db
    -rw-r-----+ 1 docker users 32768 Jan 8 18:38 nzbdrone.db-shm
    -rw-r-----+ 1 docker users 1998232 Jan 8 18:37 nzbdrone.db-wal
    -rw-rw----+ 1 docker users 3 Jan 8 15:05 nzbdrone.pid
    -rw-r-----+ 1 docker users 66898 Jan 8 14:34 nzbget.conf

    Hello!
    I've just upgraded from a raspberry pi 3 to a 4, and from omv 3 (or maybe 4) to 5. On my last setup I had Docker working with some containers, but I cannot get it to work now, using the same settings as before.
    So, I installed Docker and Portainer from the OMV-Extras GUI, then I pasted the docker-compose section from https://hub.docker.com/r/linuxserver/nzbget/ under Add stack in Portainer and replaced PUID, PGID with the values returned by id docker (uid=1001(docker) gid=100(users) groups=100(users),992(docker)).
    The volumes I set as - /sharedfolders/Docker:/config and - /sharedfolders/Downloads:/downloads.
    Lastly I pressed Deploy stack.
    The log for nzbget reads:
    "
    [s6-init] making user provided files available at /var/run/s6/etc...exited 0.



    [s6-init] ensuring user provided files have correct perms...exited 0.



    [fix-attrs.d] applying ownership & permissions fixes...



    [fix-attrs.d] done.



    [cont-init.d] executing container initialization scripts...



    [cont-init.d] 01-envfile: executing...



    [cont-init.d] 01-envfile: exited 0.



    [cont-init.d] 10-adduser: executing...





    -------------------------------------



    _ ()



    | | ___ _ __



    | | / __| | | / \



    | | \__ \ | | | () |



    |_| |___/ |_| \__/







    Brought to you by linuxserver.io



    We gratefully accept donations at:



    https://www.linuxserver.io/donate/



    -------------------------------------



    GID/UID



    -------------------------------------





    User uid: 1001



    User gid: 100



    -------------------------------------





    [cont-init.d] 10-adduser: exited 0.



    [cont-init.d] 30-config: executing...



    [cont-init.d] 30-config: exited 0.



    [cont-init.d] 99-custom-files: executing...



    [custom-init] no custom files found exiting...



    [cont-init.d] 99-custom-files: exited 0.



    [cont-init.d] done.



    [services.d] starting services



    [services.d] done.



    [INFO] nzbget 21.0 server-mode
    "


    Sorry, couldn't figure out how to make that look better...
    Anyone with the patience to tell me where and how to look for where I did bad?

    Thanks for your help @macom!
    It seems I had a lot of unused docker images taking up space along with several gigs of docker logs, so now, after a bit of cleanup, there's a bit more room!

    I'm running omv 4 on a raspberry pi 3, and when troubleshooting some file transfer issues, I noticed that there's no free space at all on my sd card (well, apart from about 40MB on the partition marked as boot). To my knowledge, I haven't stored anything there, and it's an 8GB card.
    Of course, I could start deleting stuff, but I'm not sure where to begin and what is safe to delete. Also I would really appreciate some help in identifying what could have caused this bloat.

    Just in case anyone with the same problem, and lack of knowing what I'm doing, as me finds this thread:
    If you're using the guide in the link above, make sure to pull the right version of the image, ie if you're using a Raspberry Pi you should pull images with armhf in the prefix. Just search for the plugins name in the search box on the main Docker page and choose the right version there, don't just use the "Docker images repo" page. Hopefully this saves someone a couple of days of free time wondering what exited(1) means...