Airsonic-advanced mkdir Permission denied

I got airsonic running with no problem I just stopped it to try airsonic_advanced but ran into this I google it got this https://github.com/airsonic-ad…sonic-advanced/issues/513

airsonic advanced mkdir: cannot create directory '/var/airsonic/transcode' : Permission denied

but wondering maybe I got this issue because i believe my containers are not in var anyway I am using PUID=1000
PGID=100 how to fix this issue?

According to https://github.com/airsonic-advanced/airsonic-advanced the user and group should ba as root this way it is running

Zitat

Please note that for Docker images, the volume mounting points have changed and are different from Airsonic. Airsonic mount points are at /airsonic/* inside the container. Airsonic-Advanced tries to use the same volume locations as the default war image at /var/* in order to remain consistent if people want to switch between the containers and non-containers.

• Music:/airsonic/music -> Music:/var/music
• Podcasts:/airsonic/podcast -> Podcasts:/var/podcast
• Playlists:/airsonic/playlists -> Playlists:/var/playlists
• /airsonic/data -> /var/airsonic

Also note that the Docker image will by default run as user root (0), group root (0), and so any files created in the external volume will be owned as such. You may change the user running the internal process in one of two ways:

• Specifying --user when invoking the docker run command, and providing it with one or both in the format uid:gid
• Specifying the PUID or PGID environment variables to the container image when invoking the docker run command (-e PUID=uid -e PGID=gid)

But the path are completely different airsonicadvanced/airsonic-advanced:latest and lscr.io/linuxserver/airsonic-advanced

https://hub.docker.com/r/airsonicadvanced/airsonic-advanced and https://docs.linuxserver.io/images/docker-airsonic-advanced

and for me the latest linuxserver is easier to use!

With https://docs.linuxserver.io/images/docker-airsonic-advanced this config is working my stack isversion: "2.1"
services:
airsonic:
image: lscr.io/linuxserver/airsonic-advanced
container_name: airsonic-advanced
environment:
- PUID=1000
- PGID=100
- TZ=America/Los_Angeles
      
volumes:
- /srv/dev-disk-by-uuid-37d059e6-8189-404a-967b-53afec96bf4f/AppData/airsonic:/config
- /srv/dev-disk-by-uuid-a8d62abf-6358-488e-9239-7e1e82738c84/media/Music/Loosless:/music
- /srv/dev-disk-by-uuid-a8d62abf-6358-488e-9239-7e1e82738c84/media/Music/playlist:/playlists
- /srv/dev-disk-by-uuid-a8d62abf-6358-488e-9239-7e1e82738c84/media/Music/podcasts:/podcasts
      
ports:
- 4040:4040
- 4041:4041 #UPnp
    
      
restart: unless-stopped

With https://hub.docker.com/r/airsonicadvanced/airsonic-advanced my stack is

---
version: "3"
services:
airsonic:
image: airsonicadvanced/airsonic-advanced:latest
container_name: airsonic-advanced2
environment:
- PUID=0
- PGID=0
- TZ=America/Los_Angeles
      
volumes:
- /srv/dev-disk-by-uuid-37d059e6-8189-404a-967b-53afec96bf4f/AppData/airsonic-advanced2:/var/airsonic
- /srv/dev-disk-by-uuid-a8d62abf-6358-488e-9239-7e1e82738c84/media/Music/Loosless:/var/music
- /srv/dev-disk-by-uuid-a8d62abf-6358-488e-9239-7e1e82738c84/media/Music/playlist:/var/playlists
      
      
ports:
- 4040:4040
- 4041:4041 #UPnp
    
      
restart: unless-stopped

I am aware I running it as root, but i cannot have it run otherwise

mkdir: cannot create directory ‘/var/airsonic/transcode’: Permission deniedDocker USER id: 0Docker PUID env: 1000Docker USER group: 0Docker PGID env: 100usermod: no changesProcess will run as:User: 1000

of course now in the UI, I got a red warning

"Warning! The Airsonic process is running as the root user. Please consider changing this."

I have the feeling this the real advanced one, since the san was instant compare to the linuxserver.io witch took as long as the old airsonic to scan.

Zitat von KM0201

Is there some reason not to use the Linuxserver container? I just set it up and reverse proxy'd it in less than 5min, and it seems just like the old airsonic.

The main reason https://github.com/airsonic-advanced/airsonic-advanced at the docker section they give the link to DokerHub; https://hub.docker.com/r/airsonicadvanced/airsonic-advanced by the way they mention a different mount point at /var/*

and my reverse proxy is also working at https://airsonic-advanced2.My_domain.duckdns.org/index

Zitat von Zoki

What are the permissions of /srv/dev-disk-by-uuid-37d059e6-8189-404a-967b-53afec96bf4f/AppData/airsonic-advanced2

stat /srv/dev-disk-by-uuid-37d059e6-8189-404a-967b-53afec96bf4f/AppData/airsonic-advanced2

You were right the folder owner was root rwxr-sr-x 2755 I changed to rwxrwsr-x 2775 group 100 and owner 1000 and in the stack - PUID=1000
PGID=100 everything is fine now.

Thank you to both of you