I am experiencing the same issue.

For me the issue occurs with command: asdf local ruby 3.2.2

/opt/asdf-vm/lib/functions/versions.bash: line 78: /home/foorbar/path-to-current-directory//home/foobar/.config/asdf/tool-versions: No such file or directory

It seems like the path to current directory is added to the ASDF_DEFAULT_TOOL_VERSIONS_FILENAME.

Environment:

OS:
Linux  5.15.0-105-generic #115~20.04.1-Ubuntu SMP Mon Apr 15 17:33:04 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

SHELL:
zsh 5.8 (x86_64-ubuntu-linux-gnu)

BASH VERSION:
5.0.17(1)-release (x86_64-pc-linux-gnu)

ASDF VERSION:
failing with both v0.10.2 and v0.14.0

ASDF INTERNAL VARIABLES:
ASDF_DEFAULT_TOOL_VERSIONS_FILENAME=/home/foobar/.config/asdf/tool-versions
ASDF_DATA_DIR=/home/foobar/.local/share/asdf
ASDF_DIR=/opt/asdf-vm
ASDF_CONFIG_FILE=/home/foobar/.config/asdf/asdfrc

ASDF INSTALLED PLUGINS:
ruby                        https://github.com/asdf-vm/asdf-ruby

I fell to the same rabbit hole when I started to use asdf.

ASDF_DEFAULT_TOOL_VERSIONS_FILENAME is the name you are using in all folders, like .nvmrc, not the path that defines the global tool versions.

I've been trying to get my $HOME tidy of all extra files, but it seems that global .tool-versions file should be located in $HOME/.tool-versions.

My solution was to symlink $HOME/.dotfiles/base/tool-versions to $HOME/.tool-versions. It's not as clean as I'd like, but seems to work.

In fact you misinterpret the ASDF_DEFAULT_TOOL_VERSIONS_FILENAME value (like I did for few hours). The environment variable manage only the file name, not the full path... Once you understand that you better understand why you have "/anyfolder//folder-you-wish/.tool-versions" in the error message.

So to fix that I use

WORKDIR /opt ,

Then

source /opt/asdf/asdf.sh
asdf plugin-add "${plugin}"
asdf install 
asdf global "${plugin}"

And finally, to avoid sourcing asdf (which is totaly unuseful after the command above) just add

PATH="/opt/asdf/shims:xxxx"

And bash will find your asdf bin automatically

Would it be better if this environment variable was named ASDF_TOOL_VERSIONS_DEFAULT_FILENAME?

We need to make it clear to users that it sets the default filename and not the default .tool-versions file itself.

I've been trying to get my $HOME tidy of all extra files, but it seems that global .tool-versions file should be located in $HOME/.tool-versions.

My solution was to symlink $HOME/.dotfiles/base/tool-versions to $HOME/.tool-versions. It's not as clean as I'd like, but seems to work.

@ivuorinen I think this will eventually be handled by #687

Awesome! That will indeed fix the problem I was experiencing!

And the renaming of the env would really help with the confusion. 👍 from me!

This is fixed by #2101. It will go out in the next patch release as it's backward compatible. I expect the next release to be tagged about a month from now.