🐞 Bug: Failed to create project using "Projects"

[vitalii-skliar]

Bug Description

System message appear: Failed to create project "app" Failed to create project: failed to create project directory: mkdir /app/data/projects/app: permission denied.

the "project" folder is empty

user@userserv:/app/data/projects$ ls -a
.  ..
user@userserv:/app/data/projects$

Steps To Reproduce

1. Go to "Projects".
2. Write a name for project (didn't matter do you edit compose and env file the result the same)
3. See error

Expected Behavior

Project created and displayed in "Projects" like on page

Actual Behavior

error with message "Failed to create project "app" Failed to create project: failed to create project directory: mkdir /app/data/projects/app: permission denied" appear

Screenshots

Arcane Version

v1.18.1

Installation Method

Docker Compose (Recommended)

Environment Type

Local Docker (Single instance)

Database Type

SQLite (Default)

Operating System

Linux

Docker Version

Docker version 29.4.2, build 055a478

Browser & Version

No response

Relevant Logs or Error Messages

May 03 10:49:00.040 INF Job starting name=gitops-sync schedule="0 */1 * * * *"
May 03 10:49:00.040 INF GitOps sync run started
May 03 10:49:00.041 INF GitOps sync run completed
May 03 10:49:00.041 INF Job finished name=gitops-sync
May 03 10:50:00.051 INF Job starting name=gitops-sync schedule="0 */1 * * * *"
May 03 10:50:00.051 INF Job starting name=environment-health schedule="0 */2 * * * *"
May 03 10:50:00.051 INF environment health check started
May 03 10:50:00.051 INF GitOps sync run started
May 03 10:50:00.052 INF GitOps sync run completed
May 03 10:50:00.052 INF Job finished name=gitops-sync
May 03 10:50:00.096 INF environment health check completed checked=1 online=1 offline=0 remote_sync_queued=0
May 03 10:50:00.096 INF Job finished name=environment-health
May 03 10:51:00.030 INF Job starting name=gitops-sync schedule="0 */1 * * * *"
May 03 10:51:00.031 INF GitOps sync run started
May 03 10:51:00.031 INF GitOps sync run completed
May 03 10:51:00.031 INF Job finished name=gitops-sync
May 03 10:52:00.061 INF Job starting name=environment-health schedule="0 */2 * * * *"
May 03 10:52:00.061 INF Job starting name=gitops-sync schedule="0 */1 * * * *"
May 03 10:52:00.061 INF environment health check started
May 03 10:52:00.061 INF GitOps sync run started
May 03 10:52:00.062 INF GitOps sync run completed
May 03 10:52:00.062 INF Job finished name=gitops-sync
May 03 10:52:00.108 INF environment health check completed checked=1 online=1 offline=0 remote_sync_queued=0
May 03 10:52:00.108 INF Job finished name=environment-health
May 03 10:52:04.750 INF HTTP error: 500 internal server error request.method=POST request.host=192.168.3.5:3552 request.path=/api/environments/0/projects request.query="" request.params=map[id:0] request.route=/api/environments/:id/projects request.referer=http://192.168.3.5:3552/projects/new request.length=737 response.latency=1.082089ms response.status=500 response.length=233

Docker Compose Configuration

services:
  nginx:
    image: nginx:alpine
    container_name: nginx_service
    env_file:
      - .env
    ports:
      - "8080:80"
    volumes:
      - nginx_data:/usr/share/nginx/html
    restart: unless-stopped

volumes:
  nginx_data:
    driver: local

Environment Configuration (.env file)

# Environment Variables
# These variables will be available to your project services
# Format: VARIABLE_NAME=value

# Web Server Configuration
NGINX_HOST=localhost
NGINX_PORT=80

# Database Configuration
POSTGRES_DB=myapp
POSTGRES_USER=myuser
POSTGRES_PASSWORD=mypassword
POSTGRES_PORT=5432

# Example Additional Variables
# API_KEY=
# SECRET_KEY=
# DEBUG=false

Additional Context

It didn't matter whether I edited the compose and env files; the results were the same. I tried using other compose and env files, but the results stayed the same. This is a fresh Arcane installation after removing all images and containers.

[kmendell]

The filesystem in which the porject directory is mounted is not writeable, you will have to chmod that directory to the correct user, or ste the PUID and PGID in the container to whoever owns that directory.