flyctl is not in your PATH

1 
curl -L https://fly.io/install.sh | sh

”flyctl was installed successfully to /home/circleci/.fly/bin/flyctl
flyctl is not in your PATH. Would you like to add it automatically? (Y/n)

Exited with code exit status 1”

This started happening today.

I’ve already tried adding “-s – -y” and “echo ‘export PATH=“/home/circleci/.fly/bin:$PATH”’ >> $BASH_ENV “ with no success.

Any ideas?

2

Hey there! We updated our script to help some devs not used to CLI that had some trouble setting their profiles themselves.

I see you’re using CircleCI. We added these variants too:

# Regular command with interactivity
curl -L https://fly.io/install.sh | sh

# Non interactive (defaults to no)
curl -L https://fly.io/install.sh | sh -s -- --non-interactive

# Non interactive but also setups the PATH (as if 'yes' was the response)
curl -L https://fly.io/install.sh | sh -s -- --non-interactive --setup-path

Can you give either a try?

1 Like
3

yep the last one fixed it, thanks!

1 Like
5

Oh dear, this change broke my CI! Is it worth my pinning CI installs to a specific flyctl version?

6

maybe, but not for this reason, as the flyctl installer is not versioned.

8

Ah right, so it might be better to install the tarball then instead? I just spotted the releases page.

9

yes, that should be fine! all the install script is doing is downloading a release binary and putting it in the right place. I do recommend checking the flyctl_releases API to get the latest non-yanked release (see the script)

10

just flagging that this change broke our continuous deployments in two of our companies. It’d be great to have a reliable option for CI workflows or giving a heads up about this type of changes.

11

Did you try installing via tarball (see GitHub releases page)? I think that would fix it, at the cost of needing to manually upgrade and test newer versions.

12

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.