Incorrect symbolic path of cache file when config cache path as relative

[ekko3add7]

I had configured the cache dir as the relative path and type as symbolic.
Why are the file paths combined with an absolute path and relative path?

cat .dvc/config

[cache]
dir = ../../dvc-test
type = "symlink,copy"

ls -l aaa

1.txt -> /home/ekko.chang/dev/test/data-test/.dvc/../../dvc-test/d4/1d8cd98f00b204e9800998ecf8427e
2.txt -> /home/ekko.chang/dev/test/data-test/.dvc/../../dvc-test/d4/1d8cd98f00b204e9800998ecf8427e

[efiop]

Definitely a bug on our side. Need to take a closer look. In the mean time, this works fine for you, right? Just visually looks odd?

[ekko3add7]

Hello @efiop
It is a little bit problem when I bind these data files into the container because the real data path is mounted on the host from a remote NAS server.
Of course, it could be solved with another workaround, just confirm the problem with you.

[efiop]

@ekko3add7 With bind mounts, I guess the problem here is not so much .. in the path, but more the fact. that we use use symlinks to an absolute path, right?

[ekko3add7]

@efiop yes, as I expect the symlinks as relative path should be like this:
1.txt -> ../../dvc-test/d4/1d8cd98f00b204e9800998ecf8427e

[karajan1001]

Create an issue for it?