Docker and network mounted shares

If you are able to see some directories inside that share but not the files then that looks to me like a permission problem.

Check the permission flags that you have from within LE for the directory /storage/music where the share is mounted and also for the shared contents. If the directories are not at least 755 (drwxr-xr-x) that may be the problem since containers use uid=65534, gid=100.

Alternatively you could try adding the docker parameter -v /storage/music:/music in the portainer setup or the addon's additional config page to mount that directory inside the container as /music, but I'm not sure if this will work with a mount point of a share instead of a directory in the filesystem.

Alternatively you could also mount that same share again from within the container.

You did not say what method (nfs, smb, etc.) and you did not say how they are mounted (systemd?)

If systemd, set its service to start before the docker service

Also fyi, linuxserver does not recommend or support config files to reside on remote shares. Media folders however can be on remote shares.

Quote from extremeaudio

Sorry, forgot to mention but I am using autostart to mount remote nfs volumes.

Then you could try hacking something like this using kodi's jsonrpc interface to disable and reenable the container. Not pretty but should work while a you look for a better solution.

Although, I'm not sure if containers created with portainer could be restarted this way., may be you get an idea.

/storage/.config/autostart.sh

(
<your mounts>

sleep 10

/storage/.config/addonctl.sh <docker.your_container_addon> stop
<may need to add a delay here also>
/storage/.config/addonctl.sh <docker.your_container_addon> start
) &

/storage/.config/addonctl.sh

#!/bin/sh

USER="yourkodiuser"
PASS="yourpass"
HOST="yourip:8080"

URL="http://${USER}:${PASS}@${HOST}/jsonrpc"

ADDON="$1"
STATE="$2"

function list_addons()
{
  echo 
  echo "Addons:"
  cd /storage/.kodi/addons
  ls -1d *\.*
}

function addon_exists()
{
  test -d "/storage/.kodi/addons/$ADDON" && return

  echo "Addon $ADDON not installed!"
  list_addons
  exit 1
}

function usage()
{
  echo "Usage: $0 <addon_name> <true|false|status>"
  echo "       $0 list"
  exit 1
}

function addon_enable()
{
  local STATE="$1"
  curl -D - -d \
  '{
    "jsonrpc":"2.0",
    "method":"Addons.SetAddonEnabled",
    "params":
    {
      "addonid":"'"${ADDON}"'",
      "enabled":'"${STATE}"'
    },
    "id":1
  }' \
  -H 'Content-Type: application/json' \
  "$URL"
}

function status()
{
  addon_exists

#      "properties":["enabled","version","name","description","dependencies","author"]
  curl -D - -d \
  '{
    "jsonrpc":"2.0",
    "method":"Addons.GetAddonDetails",
    "params":
    {
      "addonid":"'"${ADDON}"'",
      "properties":["enabled","version","name","dependencies","author"]
    },
    "id":1
  }' \
  -H 'Content-Type: application/json' \
  "$URL"

  echo
}

case "$ADDON" in
  list)          list_addons
                 exit 0;;
esac

case "$STATE" in
  status)              status ;;
  enable|true|start)   addon_enable "true" ;;
  disable|false|stop)  addon_enable "false" ;;

  *) usage ;;
esac

Quote from extremeaudio

[user='138']

Sorry, forgot to mention but I am using autostart to mount remote nfs volumes. System.d prolongs boot time if the remote server is down.

It's either going to wait until remote paths are mounted, or it's going to start without them (as it does now). Can't have it both ways.

Add TimeoutSec= parameter to your mount unit, see end of systemd.mount man page.