🐞 Bug: Projects Volumes not documented (from what I can see).

[ZenDeuo]

Bug Description

I'm not sure if this is a bug or a feature, either way it was annoying to find out that when I specify Volumes within my Docker Compose in the Projects section of Arcane; that these Volumes that I specified don't actually get used and Arcane instead appends the Projects name right to the front of each Volume which is really nice for a lot of people, I'm sure, but annoying for me to find out just now rather than it being documented.
I had recently setup a new Server and migrated over a couple Docker Containers from the last Server and now I have to re-migrate the Volumes from their current names: OnlyOffice_Logs, OnlyOffice_Fonts etc
To their new names cloud_OnlyOffice_Logs, cloud_OnlyOffice_Fonts etc

I had only noticed today because I was looking at Arcane today to ensure all my Containers were all running perfectly and noticed that the Volumes section of Arcane had a bunch of non-used Volumes which I know I had definitely specified within each of the Projects within Arcane. It just doesn't seem to work as intended in my mind, when I think of a Docker Compose I think it's going to use the exact names I set unless specified elsewhere that it will not which I've not been able to find in the Documentation so I figured all would have worked fine during my migration and my data still be kept as normal.

So I wouldn't necessarily called this a bug of sorts but could it be made a little bit clearer somewhere so that someone else doesn't trip over this the same way I did?

Thank you!
Ryan :)

Steps To Reproduce

1. Open Arcane.
2. Go To Projects.
3. Make A New Project.
4. Run Anything You Want And Add A Volume To It.
5. Run The Container.
6. Volume Name Mismatch In Arcane Volumes Compared To What You Specified In Your Projects Docker Compose.

Expected Behavior

I expected it to utilize the Volume Name I provided unless it were specified elsewhere that it were not going to do so. I haven't seen anywhere it state that it was going to append the Projects' name to the front of each Volume added and I didn't expect it to do that.

Actual Behavior

It appended the Projects' name to each of the Volumes outlined in my Projects' Docker Compose file.

Screenshots

Arcane Version

v1.16.4

Installation Method

Docker Compose (Recommended)

Environment Type

Local Docker (Single instance)

Database Type

SQLite (Default)

Operating System

Linux

Docker Version

Docker version 29.3.0, build 5927d80

Browser & Version

Zen Browser 1.19b (Firefox 148.0) (aarch64)

Relevant Logs or Error Messages

No Relevant Logs or Error Messages :)

Docker Compose Configuration

services:
  OnlyOffice:
    container_name: OnlyOffice
    image: onlyoffice/documentserver:8.3.3
    restart: unless-stopped
    ports:
      - "8806:80"
    environment:
      - JWT_SECRET=REDACTED
      - ALLOW_EXTERNAL_DOMAINS=REDACTED
      - DS_DOCKER_INSTALLATION=true
      - JWT_ENABLED=true
      - JWT_HEADER=Authorization
    volumes:
      - OnlyOffice_RabbitMQ:/var/lib/rabbitmq
      - OnlyOffice_Redis:/var/lib/redis
      - OnlyOffice_Logs:/var/log/onlyoffice
      - OnlyOffice_Data:/var/www/onlyoffice/Data
      - OnlyOffice_Fonts:/usr/share/fonts/truetype/custom
      - OnlyOffice_Lib:/var/lib/onlyoffice
      - OnlyOffice_DB:/var/lib/postgresql
    security_opt:
      - label=disable

Environment Configuration (.env file)

.env not relevant regarding this matter :)

Additional Context

No Additional Information Required :)

[ZenDeuo]

Also oddly enough, I've noticed that some of the Volumes have containers randomly attached to them but these containers don't actually exist or even show up within the Arcane UI?

So I'm not sure whats up with that either haha.

[kmendell]

In order to use bolumes created outside of the compose file, you have to mark them as external.

If there are random volumes it most likely means something that wants a volume mount didnt get one.

The project name being appended to the volume is the default behavior of compose.

[ZenDeuo]

In order to use bolumes created outside of the compose file, you have to mark them as external.

Sweet, how would I go about marking the Volumes as external though?

If there are random volumes it most likely means something that wants a volume mount didnt get one.

Also there are no random volumes which I'm glad, everything has been assigned correctly.

The project name being appended to the volume is the default behavior of compose.

Probably a bit of an ask but could this also be documented for future reference if it isn't? I just feel like it would make it more clearer since in my mind Docker Compose Files in any interface would just use the Volume name I specified and not tag anything onto the front. It might sit well in the Volumes or Projects Section in the Documentation :)

Also I'm not sure if this is a bug either or I'm just silly but when a Volume is marked as unused:

If you open it up, it also says it's not in use:

You can go through the different menu's and it'll still be unused, but then when you go back it's now in use by a random container out of nowhere? :p

Thank you very much, I really appreciate the support!
Ryan