Troubleshooting

AWS credentials not found

error: no AWS credentials found

Fix: run yg configure, or set environment variables:

export AWS_ACCESS_KEY_ID=your_key
export AWS_SECRET_ACCESS_KEY=your_secret

Or run aws configure if you have the AWS CLI installed.

rsync not found

error: rsync not found

Fix:

# Linux
apt install rsync

# macOS (if not pre-installed)
brew install rsync

Missing dependencies on the VM

If your command fails because a package isn't installed, add it to .yeager.toml:

[setup]
packages = ["libpq-dev", "your-package"]

Then rebuild the VM:

yg destroy
yg up

First run is slow

Expected. The first boot takes 2–3 minutes while cloud-init installs your project's toolchain. Subsequent runs start instantly (the VM stays warm between commands).

Command keeps running after Ctrl+C

By design — Ctrl+C detaches from the output stream without killing the remote process. To actually cancel:

yg kill

To re-attach and see output:

yg logs

VM is in a bad state

yg destroy   # terminates the VM and cleans up
yg up        # fresh start

Debug output

yg --verbose <command>

Prints detailed logs including AWS API calls, SSH connection info, and rsync output.

Permissions errors (EC2)

If you see AWS permission errors, check that your IAM user has the minimum required permissions.

A quick check:

yg configure   # validates credentials and checks EC2 permissions