azukaar
[BUG]: New Directory + Icons Mount Path Issue
What happened?
I used the new directory + icons feature to change the mount path. It added /mnt/host/ as the mount path for Cosmos on Docker. However, the paths referenced in the system do not include /mnt/host/. For example, /mnt/host/srv/ should simply be /srv/.
What should have happened?
The paths should not include /mnt/host/ in the references. Instead, they should directly reference the intended paths, such as /srv/.
How to reproduce the bug?
- Go to the settings or configuration for the new directory + icons feature.
- Change the mount path to include
/mnt/host/. - Observe the paths referenced in the system (e.g.,
/mnt/host/srv/). - Notice that the paths should ideally be
/srv/without the/mnt/host/prefix.
Relevant log output
No response
Other details
This issue seems to be specific to the Docker setup for Cosmos (could be that it does not happen on barebone), where the host mapping is involved. But barebone is not released yet.
System details
- OS: Debian
- Version: since 17.0 now on 17.7
I have a similar issue.
I'm running Cosmos on an Ubuntu VM, where I have mounted shared folders under /mnt.
In Cosmos, I can easily access these mounts when setting up a new Docker configuration:
However, when I select a mount, Cosmos automatically adds/mnt/hostto the path. This creates a host folder inside Ubunutu in /mnt, preventing access to the files.
To resolve this, I have to manually remove /mnt/host from the path, after which everything works as expected.
In the Cosmos server environment, / is mounted to /mnt/host. I'm not sure what needs to be changed to fix this behavior.
This is just a UI bug and nothing serious, but it would be great if @azukaar could start working on a fix, especially for new users. @kolossboss, to fix it, you need to delete the mnt/host directory. It's a bit unusual for new users, but since this feature is still quite new, I knew why it is not right.
You can not change your system this is a bug of cosmos.