problem installing fly.io on ubuntu

1

I tried to install flyctl on ubuntu but nothing worked

Screenshot from 2023-02-20 16-34-02
Screenshot from 2023-02-20 16-34-02815Ă—107 13 KB

1 Like
2

I also ran into same problem today while installing flyctl on ubuntu. It seems there is some issue with install.sh script url.

You can download latest release from Releases · superfly/flyctl · GitHub and then install it using following commands -

wget https://github.com/superfly/flyctl/releases/download/v0.0.462/flyctl_0.0.462_Linux_x86_64.tar.gz

tar -xf flyctl_0.0.462_Linux_x86_64.tar.gz

chmod +x flyctl

sudo mv flyctl /usr/local/bin

cd /usr/local/bin

ln -s flyctl fly

After this you will be able to use fly command.

3 Likes
3

I was able to use the script to install flyctl on a brand new Ubuntu 22.04 machine:

Welcome to Ubuntu 22.04.1 LTS (GNU/Linux 5.15.0-1029-gcp x86_64)
[...]

lillian@instance-2:~$ curl -L https://fly.io/install.sh | sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1475    0  1475    0     0   1267      0 --:--:--  0:00:01 --:--:--  1268
######################################################################## 100.0%
set channel to shell
flyctl was installed successfully to /home/lillian/.fly/bin/flyctl
Manually add the directory to your $HOME/.bash_profile (or similar)
  export FLYCTL_INSTALL="/home/lillian/.fly"
  export PATH="$FLYCTL_INSTALL/bin:$PATH"
Run '/home/lillian/.fly/bin/flyctl --help' to get started

For better debugging, can you download the script wget https://fly.io/install.sh, edit the set -e line to set -ex, and run it with sh install.sh? That should give a lot more output.

1 Like
4

You can easily install flyctl from Snap Store on Ubuntu and use it

5

I actually don’t recommend using the snap-packaged flyctl; it’s very outdated (0.1.87 from September 2023), and it uses “strict” confinement so its capabilities will be quite limited. For example, it’s very likely unable to use --local-only builds as it can’t talk to the local Docker daemon.

Regards,

  • Daniel