NZBget/SABnzb - Storage premissions delte or rename files not allowed

1st Official Post

    ::ENG::

    Hello dear OMV friends,


    I currently have the following problem: if I install NZBget or SABnzb via Portainer as a Docker container, both work as far as possible, but I have no authorization to delete, move or rename data in the download folder.


    As PUID = OpenMediaVault Admin and PGID = User


    I've tried other IDs too. But the users created in OMV are not displayed at all when querying the SSH terminal "id $ user".


    The "/ config" folder of the respective container has a portainer volume and the download folder is located in a folder released in OMV (also called SAMBA) on one of the two NAS HDDs.


    My hardware:

    OMV Version: 5.6.23-1 (Usul)

    CPU: Intel Celeron J4105 @ 1.50GHz

    RMA: 16GB DDR4 SODIMM

    OMV SSD: 128GB SATA m.2 <-- only OMV & Docker Data

    Storage NAS Drives: 2x 4TB WD Red

    Kernel: Linux 5.10.0-0.bpo.8-amd64

    Docker: 5: 10/20/12 ~ 3-0 ~ debian-buster

    Portainer: 2.11.0

    _________________________________________________________________________________________________


    ::DE::

    Hallo liebe OMV Freunde,


    ich habe aktuell folgendes Problem: wenn ich NZBget oder SABnzb via Portainer als Docker Container installiere funktioniert beides soweit einwandfrei aber ich habe keine Berechtigung im Download Ordner Daten zu löschen, verschieben oder umzubenennen.


    Als PUID = OpenMediaVault Admin und PGID = User


    Ich habe auch schon andere IDs versucht. Aber die in OMV angelegten Benutzer werden bei der SSH Terminal abfragen "id $user" gar nicht angezeigt.


    Der "/config" Ordner der jeweiligen Container hat ein einges Portainer Volume und der Download Ordner befindet sich auf einem in OMV Freigegebenen (auch als SAMBA) Ordner auf einer der beiden NAS HDDs.


    Meine Hardware:

    OMV Version: 5.6.23-1 (Usul)

    CPU: Intel Celeron J4105 @ 1.50GHz

    RMA: 16GB DDR4 SODIMM

    OMV SSD: 128GB SATA m.2 <-- nur für OMV & Docker

    Storage NAS Drives: 2x 4TB WD Red

    Kernel: Linux 5.10.0-0.bpo.8-amd64

    Docker: 5:20.10.12~3-0~debian-buster

    Portainer: 2.11.0

    • Official Post

    You shouldn't use admin on a container unless absolutely necessary. Take a look at this.

    [How to] Prepare OMV to install docker applications

    What permissions does the download folder have?


    If you change the PUID (and you will have to), you will most likely have to change the permissions inside the named volume too.

    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.

    When are you going to post the complete set of things you put into Portainer to create this container? You should be working from the documentation available for the docker image you are using that shows suggested sample docker run, docker compose, docker create or stack files. All of these sample files need to be corrected to agree with your exact use case. They can not be used as is. Simply put, there are no mind readers here and prying this information out of users looking for help one piece at a time is not helpful, delays you from arriving at a solution, and discourages those who could help you from actually helping you.


    By far, the most commonly seen problem with dockers revolves around a mismatch between the user:group (PUID:PGID) the container runs as and the ownership and permissions on the files and folders it needs to operate on. This will bite you every single time. <- It is impossible to overemphasize this.


    As already stated, using the OMV Admin PUID=998 to run containers is a mistake. I don't know where this idea came from originally, but it is constantly being rediscovered and applied.

    --
    Google is your friend and Bob's your uncle!


    A backup strategy is worthless unless you have a verified to work by testing restore strategy.


    OMV AMD64 7.x on headless Chenbro NR12000 1U Intel Xeon CPU E3-1230 V2 @ 3.30GHz 32GB ECC RAM.

    OMV AMD64 8.x on headless Tyan Thunder SX GT86C-B5630 1U Server with Intel Xeon Silver 4110 CPU @ 2.10GHz & 32GB DDR4 ECC RAM.

    THX for this Information.


    But it is a premission problem, i ask for an solution for the folder premissions.


    As far as I understand, the container owner is also the one who has the rights to the data. So the OMVAdmin would also be legally able to delete the data created by the container.

    If that's wrong, who would be the right user so that the normal user can then also delete the data on the data carriers? My Main User (Chris) is in OMV also in the OVMAdmin Group.


    But here is the data for creating the container:


    post stat /my_harddiskdrive

    and ls -l /my_harddiskdrive/


    You are mixing up user and gtoup of a file and file permissions.


    And you do not seem to care for security :-

    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.

    If you feel safe to open your server to the outside world with a user access than can cripple ALL your DATA, then continue as you are.


    If not, then remove your user from those groups, chown the folders to the user you need to run (id 1000 or bigger, gid can be 100)

    chown recursively to 1000:100 and relaunch the YML.


    Done

    Quote from Chris007

    the Server is only in local network at home, no remote access and so on

    So, why do you need a nzbget client?!?

    you will get the uid of the user to use by id the_user_name.

    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