few-dress-69520
07/03/2025, 7:56 AMmetaflow environment resolve --arch osx-arm64 --arch linux-64 --force -r requirements.txt --alias my_test_env
There is the option of using fetch_at_exec
to determine the name of the named environment at runtime. Then I could resolve the environments for both architectures and give them different aliases, e.g. my_test_env:<arch>
, and define through runtime information, which is the correct one. I'm just wondering whether this is an appropriate way of doing it. Is there a better way?dry-beach-38304
07/03/2025, 9:21 AMdry-beach-38304
07/03/2025, 9:22 AMdry-beach-38304
07/03/2025, 9:22 AMfew-dress-69520
07/03/2025, 9:51 AMmetaflow environment show
by supplying the full hashes (and adding --arch linux-64 in one case). But when searching for the alias, only the osx-arm64 version shows up. For the linux version I get
β metaflow environment show --arch linux-64 my_test_env
Metaflow (2.15.18+netflix-ext(1.2.3))
### Environment for 'my_test_env' (arch 'linux-64') was not found
I tried to switch the order of the resolution to see whether the other one would get aliased in that case, but then I get this seemingly unrelated error
β metaflow environment resolve --arch linux-64 --arch osx-arm64 --force -r requirements.txt --alias my_test_env
Metaflow (2.15.18+netflix-ext(1.2.3))
Resolving 2 environments ...Pretty-printed STDOUT:
Could not solve for environment specs
The following package could not be installed
ββ python 3.11.10 is not installable because it requires
ββ __glibc >=2.17,<3.0.a0 , which is missing on the system.
{
"success": false
}
dry-beach-38304
07/03/2025, 9:57 AMMETAFLOW_DEBUG_CONDA=1 metaflow environment resolve β β¦
and sned me the output. I can try taking a look (likely in the next few days; I am traveling tomorrow so may be a bit slower to resond).few-dress-69520
07/03/2025, 10:22 AM