Skip to content

Commit 4d911f0

Browse files
Add instructions to fix bad binary downloads
Added section to the readme to address bad binary downloads resulting from using
1 parent 96686a8 commit 4d911f0

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

README.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -97,5 +97,20 @@ Foreman is a work in progress tool and has some known issues. Check out [the iss
9797

9898
If you have issues with configuration, you can delete `~/.foreman` to delete all cached data and start from scratch. This directory contains all of Foreman's installed tools and configuration.
9999

100+
### `Bad CPU type` Error
101+
If you're using foreman version 1.0.4 or older on a non-M1 Mac, you may have encounter an error that looks like this:
102+
```
103+
an error happened trying to run `github.com/some-org/some-tool@^1.2.3` at `/Users/some-user/.foreman/tools/some-org__some-tool-1.2.3` (this is an error in Foreman): Bad CPU type in executable (os error 86)
104+
```
105+
106+
In this case, your foreman installation has mistakenly downloaded an incompatible version of the tool binary due to [an error in the binary file selection logic](https://github.com/Roblox/foreman/pull/53).
107+
108+
To fix this error, take the following steps:
109+
1. Upgrade your version of `foreman` per [the instructions above](#upgrading).
110+
2. Delete the `~/.foreman/tool-cache.json` file and the `~/.foreman/tools/` folder (and its contents). This should remove any invalid binaries that foreman has cached.
111+
3. Run `foreman install` to redownload all relevant tools.
112+
113+
Your downloaded tools should now work correctly.
114+
100115
## License
101116
Foreman is available under the MIT license. See [LICENSE.txt](LICENSE.txt) or <https://opensource.org/licenses/MIT> for details.

0 commit comments

Comments
 (0)