Hi, I've recently acquired an M1 MacBook, but have been unable to get Bass running on it.
I installed "Docker Desktop" (through Brew Cask brew install homebrew/cask/docker) and Bass 0.10.0. However, whenever I try to run bass it is unable to start the Buildkitd container. The container appears to get stuck in a restart loop.
The error from Bass:
init buildkit runtime for platform os=linux, arch=any: list buildkit workers: failed to list workers: Unavailable: connection error: desc = "transport: Error while dialing dial unix /run/buildkit/buildkitd.sock: connect: no such file or directory"
Tip: if this error is too cryptic, please open an issue:
https://github.com/vito/bass/issues/new?labels=cryptic&template=cryptic-error-message.md
The log from the container:
time="2022-10-09T15:38:09Z" level=info msg="auto snapshotter: using overlayfs"
buildkitd: invalid argument
time="2022-10-09T15:38:10Z" level=info msg="auto snapshotter: using overlayfs"
buildkitd: invalid argument
time="2022-10-09T15:38:10Z" level=info msg="auto snapshotter: using overlayfs"
buildkitd: invalid argument
time="2022-10-09T15:38:11Z" level=info msg="auto snapshotter: using overlayfs"
buildkitd: invalid argument
time="2022-10-09T15:38:12Z" level=info msg="auto snapshotter: using overlayfs"
buildkitd: invalid argument
time="2022-10-09T15:38:15Z" level=info msg="auto snapshotter: using overlayfs"
buildkitd: invalid argument
time="2022-10-09T15:38:18Z" level=info msg="auto snapshotter: using overlayfs"
buildkitd: invalid argument
time="2022-10-09T15:38:25Z" level=info msg="auto snapshotter: using overlayfs"
buildkitd: invalid argument
time="2022-10-09T15:38:39Z" level=info msg="auto snapshotter: using overlayfs"
buildkitd: invalid argument
time="2022-10-09T15:39:05Z" level=info msg="auto snapshotter: using overlayfs"
buildkitd: invalid argument
time="2022-10-09T15:39:57Z" level=info msg="auto snapshotter: using overlayfs"
buildkitd: invalid argument
time="2022-10-09T15:40:57Z" level=info msg="auto snapshotter: using overlayfs"
buildkitd: invalid argument
Additional context
The Docker volume bass-buildkit is created and marked as "in use".
Probably unrelated, and I'm not sure if this is intentional/known, but the container runs on x86 emulation mode, i.e. it isn't running a native ARM version of the container.
I have Rosetta installed, so I suspect that this wouldn't be an issue.
Describe the bug
Hi, I've recently acquired an M1 MacBook, but have been unable to get Bass running on it.
I installed "Docker Desktop" (through Brew Cask
brew install homebrew/cask/docker) and Bass 0.10.0. However, whenever I try to runbassit is unable to start the Buildkitd container. The container appears to get stuck in a restart loop.The error from Bass:
The log from the container:
Additional context
bass-buildkitis created and marked as "in use".Screenshots
Click to view screenshots.