You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.2
The text was updated successfully, but these errors were encountered:
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?
/mnt/host/
./mnt/host/srv/
)./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
The text was updated successfully, but these errors were encountered: