`metaflow-dev up`: incorrect shell in Makefile and AWS shared credentials

[Julien-Agentic]

Currently exploring Metaflow to compare with our AWS Sagemaker AI stack.
Really enjoying the UX and interested by all the features available.

Started locally with metaflow-dev up.
Went pretty smoothly except for two issues I met. I am sharing them here in case that helps someone.

1) Makefile shell issue?

When running uv run metaflow-dev up, met the following error:

> uv run metaflow-dev up
🔍 Checking Docker daemon...
✅ Docker is running
🔍 Checking if gum is installed...
✅ gum is already installed.
🔧 Setting up Minikube v1.32.0 cluster...
✅ Minikube v1.32.0 cluster is already running
🎉 Minikube v1.32.0 cluster is ready!
📥 Installing Helm v3.14.0...
Helm v3.19.2 is already latest
✅ Helm installation complete
🚀 Starting up (may require sudo access)...
/home/ju-pc/Developer/mlops/.venv/share/metaflow/devtools/.devtools/start.sh: line 5: set: -g: invalid option
set: usage: set [-abefhkmnptuvxBCEHPT] [-o option-name] [--] [-] [arg ...]

Had to apply the following patch to Metaflow/devtools/Makefile

- @echo 'eval $$($(MINIKUBE) docker-env)' >> $(DEVTOOLS_DIR)/start.sh
+ @echo 'eval $$(SHELL=/bin/bash $(MINIKUBE) docker-env)' >> $(DEVTOOLS_DIR)/start.sh

Running the script in bash was not solving the issue.

2) AWS credentials conflict?

When running the example 05:

❯ uv run metaflow-tutorials/05-hello-cloud/hello-cloud.py run
Metaflow 2.19.7 executing HelloCloudFlow for user:ju-pc
Validating your flow...
    The graph looks good!
Running pylint...
    Pylint is happy!
2025-11-22 21:05:06.205 Workflow starting (run-id 2), see it in the UI at http://localhost:3000/HelloCloudFlow/2
    S3 access denied:
    s3://metaflow-test/metaflow/HelloCloudFlow/2/_parameters/2/0.attempt.json

Had to use export AWS_SHARED_CREDENTIALS_FILE= && uv run metaflow-tutorials/05-hello-cloud/hello-cloud.py run instead.

Config is as follow:

Platform: WSL2
Shell: fish 4.2.0
Python version: 3.14.0
Package manager uv 0.8.3
Metaflow 2.19.7