🐞 Bug: In Arcane 1.17.1, update seems to have broken permissions which were working before.

[bestonephoenix]

Bug Description

In Arcane 1.17.1, update seems to have broken permissions which were working before.

for example: when attempting to create a new project, saving fails with the error:
Failed to create project: failed to create project directory: mkdir /app/data/projects/test: permission denied
same when attempting to edit a project compose or env.

Weirdly it doesn't seem to have affected other stacks connected through arcane headless.

System (please complete the following information):
OS: Debian GNU/Linux - Version: 13 as LXC in Proxmox, Docker
docker logs arcane don't show any entry.

Steps To Reproduce

Create New Project
Click (+) Create New Project
Expected behavior
Should save - as it did in 1.16 and before

Expected Behavior

W access as before

Actual Behavior

R only

Screenshots

No response

Arcane Version

1.17.1

Installation Method

Docker Compose (Recommended)

Environment Type

Local Docker (Single instance)

Database Type

SQLite (Default)

Operating System

Linux

Docker Version

29.4.0

Browser & Version

Chrome 145

Relevant Logs or Error Messages

`Failed to create project: failed to create project directory: mkdir /app/data/projects/test: permission denied

Docker Compose Configuration

services:
  arcane:
    image: ghcr.io/getarcaneapp/arcane:latest
    container_name: arcane
    ports:
      - '3552:3552'
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - arcane-data:/app/data
      - ./arcane:/app/data/projects
    environment:
      - APP_URL=http://192.168.178.78:3552
      - PUID=1000
      - PGID=1000
      - ENCRYPTION_KEY=xxx
      - JWT_SECRET=xxx
      - GPU_MONITORING_ENABLED=true

    networks:
      - pangolin
    restart: unless-stopped

volumes:
  arcane-data:

networks:
  pangolin:
    name: pangolin
    external: true

Environment Configuration (.env file)

Additional Context

worked flawlessly under 1.16.4

[Profex]

I was facing exactly the same issue. In my case, only the main Arcane installation was affected, while multiple connected Arcane headless instances continued to work without any problems.

When I checked the filesystem permissions on the main Arcane instance, I noticed that all related files and directories were set to 555 (r-xr-xr-x). In contrast, the working Arcane headless instances had permissions set to 755 (rwxr-xr-x).

After updating the permissions of all Arcane-related files and directories on the main instance to 755, everything started working as expected again. For example, I can now edit compose and environment files via the GUI, which was not possible before (saving changes failed prior to the fix).

[bestonephoenix]

Thanks - I applied the same permissions, but it refuses to edit / add any files in its own container it seems?

When creating new projects it does attempt somehow to create a folder and fails. The /projects folder i mounted has full r/w access...
Failed to create project: failed to create project directory: mkdir /app/data/projects/orcaslicer: permission denied
The same error is when I try to edit existing config / env files

[Profex]

Maybe your file/folder ownership is still wrong (e.g. wrong user)? All my Arcane related files are owned by docker:docker, and I am supplying the corresponding UID and GID of the "docker" user/group to Arcane via .env file (PUID,PGID).

See e.g. docker compose example : https://github.com/getarcaneapp/arcane/blob/main/docker/examples/compose.basic.yaml

    environment:
      # Optional: run Arcane as a specific host UID/GID instead of the default runtime user.
      # When using the mounted Docker socket, Arcane will map the socket group automatically.
      # - PUID=1000
      # - PGID=1000

[bestonephoenix]

Thanks - I checked and the two PUID and PGID entries were in my compose.

I tested by commenting them out, and see there, it all works now? No idea why, but it does