Docker permissions for remotemount share

  • Hi,

    I'm looking for some help with setting up permissions (I'm assuming) correctly within OMV for docker compose.

    I successfully set up a PoC docker environment to use a local OMV share and sub folders, served via a USB flash drive connected to my OMV host - exactly as per this YT guide (16:08 onwards) :


    Externer Inhalt www.youtube.com
    Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
    Durch die Aktivierung der externen Inhalte erklären Sie sich damit einverstanden, dass personenbezogene Daten an Drittplattformen übermittelt werden. Mehr Informationen dazu haben wir in unserer Datenschutzerklärung zur Verfügung gestellt.


    I now want to take this a step further and use a shared SMB folder on my old Synology NAS as the location for my docker set up.

    I've set the the share up on the NAS, successfully mounted the SMB share using the remote mount plugin in OMV, and created the docker directories required in the share.
    The latter step was done manually from my Windows pc after mapping a drive to the new OMV share.

    The issue I am having is when I try to add the new folder locations via Services > Compose > Settings in OMV.
    I am receiving an error message when applying the changes, which I think is permissions related:


    ID: configure_compose_global_env_file

    Function: file.managed

    Name: /srv/remotemount/SynNAS_OMV_Root/RootShare/docker/compose/global.env

    Result: False

    Comment: Failed to change mode to 0600


    I'm not sure whether extra steps need to be taken with permissions on the source (Synology NAS) share side and/or extra steps need to be taken in OMV to allocate the correct permissions?

    Can anyone help with this please?

    Thanks

    Matt

  • chente

    Hat das Thema freigeschaltet.
    • Offizieller Beitrag

    There is a very common phrase here: Users always end up doing something unforeseen.

    I don't think anyone would think to configure docker directories in a remote folder, and honestly, I think it's a bad idea for many reasons. But if you insist on doing it, the problem you have is that the plugin is trying to configure root permissions on the remote resource.

  • There is a very common phrase here: Users always end up doing something unforeseen.

    I don't think anyone would think to configure docker directories in a remote folder, and honestly, I think it's a bad idea for many reasons. But if you insist on doing it, the problem you have is that the plugin is trying to configure root permissions on the remote resource.

    Thanks for the reply.
    I get what you are saying with regards running docker remotely, but I just want to run a couple of non-critical workloads - Portainer, Speedtest tracker et al for testing purposes.
    If there are issues, then I'll likely assess whether it is worth me spending hundreds of £'s on a NAS that supports docker, or DAS storage for my Raspberry Pi OMV server.
    Having said all that, I have been using docker on an EC2 instance in AWS as and when required for study purposes, for a good while with out issue....

    You mentioned the root permissions for the plugin - can you provide some extra explanation on what is required please?

    Thanks

    • Offizieller Beitrag

    hundreds of £'s

    Hundreds of pounds? That makes no sense. Docker configuration folders take up almost no space. We're talking about the configuration folders only, perhaps a container like Plex could have an extensive database, still any 100GB hard drive could be sufficient.

    Data folders could be remote if you configure them correctly and the remote resource is always online.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!