I tried to upgrade the CLI with apify upgrade and it failed to replace the apify binary. The binary being overwritten is the same process that runs the upgrade, and Linux won't let a running executable be opened for writing.
My setup: Fedora Linux (x64), with the CLI installed as a standalone binary in ~/.apify/bin, upgrading to 1.10.0.
% apify upgrade
Info: Downloading `actor` binary of the Apify CLI...
Info: Writing actor to /home/vdusek/.apify/bin/actor...
Info: Downloading `apify` binary of the Apify CLI...
Info: Writing apify to /home/vdusek/.apify/bin/apify...
Error: Failed to write the apify bundle. Please open an issue on https://github.com/apify/apify-cli/issues/new and provide the following information:
- The version you are trying to upgrade to: 1.10.0
- The system you are running on: linux x64
- The URL of the asset that failed to fetch: https://github.com/apify/apify-cli/releases/download/v1.10.0/apify-1.10.0-linux-x64
- The error: ETXTBSY: text file is busy, open '/home/vdusek/.apify/bin/apify'
Success: Successfully upgraded to 1.10.0 👍
✍️ Drafted by Claude Code
I tried to upgrade the CLI with
apify upgradeand it failed to replace theapifybinary. The binary being overwritten is the same process that runs the upgrade, and Linux won't let a running executable be opened for writing.My setup: Fedora Linux (x64), with the CLI installed as a standalone binary in
~/.apify/bin, upgrading to 1.10.0.✍️ Drafted by Claude Code