Issue running on Mac M Series?
I just installed coder, and I got this error when I tried to run a dev container template:
Error: Incompatible provider version
Provider registry.terraform.io/coder/envbuilder v1.0.0 does not have a
package available for your current platform, darwin_arm64.
Provider releases are separate from Terraform CLI releases, so not all
providers are available for all platforms. Other versions of this provider
may have different platforms supported.
13 Replies
hey @OttoVonBizMarkie, we don't currently build the envbuilder provider for the Mac M series architecture
are you intending to use this macOS device as your Coder server or just for playing around with the product?
Mainly just playing around with the product, though I wouldn't totally rule it out, it's an m4 that is probably the most powerful machine I have access to locally.
Also have it running on a linux machine.
Which actually makes me wonder, if there's two different hosts each running a server, is there a way to control both through one ui?
sounds good!
yeah I don't have an immediate fix for you but you could use a Linux VM as a workaround
yes!
you can run the Coder Control Plane (
coderd) and the Coder Provisioner Daemon (provisionerd) separately!
so, what you're referring to the "server" would be the provisioner daemonsGitHub
feat: support platforms other than Linux · Issue #26 · coder/terraf...
This provider currently only builds for GOOS=linux: GOOS=darwin CGO_ENABLED=0 go build . # github.com/docker/docker/volume/mounts ../../../go/pkg/mod/github.com/docker/[email protected]+incompatible/v...
Thanks. The Linux machine is actually a VM, though on top of Proxmox. (Possibly) one last question. I am testing what happens when I do a non graceful shutdown. After rebooting the linux machine, it seems that coder restarts, but when I try to access the url, I get {"message":"Peer is not connected."}
using "systemctl stop coder" then "coder server" will restore things to run again, but I'm wondering if there's something I can change in the configuration to ensure it runs after a reboot?
your error message does seem to say it's running under macOS though, the "
darwin" in "darwin_arm64" means macOS
are you using a try.coder.app URL?Yeah, this is now using a different linux environment that I am trying everything on now. I did use the try.coder.app url. (This might make more sense to ask in a new channel).
yes, so the
try.coder.app URL establishes a connection with your server on each startup, but the URL will change on every restart
it will show this message if you stop the server abruptly or anything like thatHmmm, interesting. So far, after "systemctl stop coder," it uses the exactly same url each time.
that is weird
anyways i think once the connection breaks it has to be started over hence why you're facing this issue
I'd recommend setting
CODER_ACCESS_URL for your long-term setupYup, that's the plan!
feel free to open another thread if you need help :-)
@Phorcys closed the thread.