Skip to content

Coder gets zsh killed on macOS (not M1) after curl installing 0.6.2 AMD64 build #2086

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sharkymark opened this issue Jun 6, 2022 · 8 comments · Fixed by #2309
Closed

Coder gets zsh killed on macOS (not M1) after curl installing 0.6.2 AMD64 build #2086

sharkymark opened this issue Jun 6, 2022 · 8 comments · Fixed by #2309
Assignees
Labels
api Area: HTTP API site Area: frontend dashboard
Milestone

Comments

@sharkymark
Copy link
Contributor

OS Information

  • OS:
  • Browser (if applicable):
  • Architecture:
  • coder --version: 0.6.2

Steps to Reproduce

curl -L https://coder.com/install.sh | sh

then run coder

Expected

the list of coder commands

Actual

markmilligan@mtmcoder ~ % coder
zsh: killed coder

Logs

After coder is installed:

`Installing v0.6.2 of the amd64 release from GitHub.

  • Reusing ~/.cache/coder/coder_0.6.2_darwin_amd64.zip
  • mkdir -p /usr/local
  • sudo mkdir -p /usr/local/bin
    Password:
  • sudo unzip -d ~/.cache/coder -o ~/.cache/coder/coder_0.6.2_darwin_amd64.zip
    Archive: /Users/markmilligan/.cache/coder/coder_0.6.2_darwin_amd64.zip
    inflating: /Users/markmilligan/.cache/coder/LICENSE
    inflating: /Users/markmilligan/.cache/coder/README.md
    inflating: /Users/markmilligan/.cache/coder/coder
  • sudo cp ~/.cache/coder/coder /usr/local/bin/coder
    Standalone release has been installed into /usr/local/bin/coder

Run Coder (temporary):
coder server --dev

Or run a production deployment with PostgreSQL:
CODER_PG_CONNECTION_URL="postgres://@/?password="
coder server`

which coder

markmilligan@mtmcoder ~ % which coder /usr/local/bin/coder

Screenshot

Notes

I'm blocked

@ketang ketang changed the title Bug: coder gets zsh killed on macOS AMD (not M1) after curl installing 0.6.2 Bug: coder gets zsh killed on macOS Intel (not M1) after curl installing 0.6.2 Jun 6, 2022
@ketang ketang changed the title Bug: coder gets zsh killed on macOS Intel (not M1) after curl installing 0.6.2 Bug: coder gets zsh killed on macOS (not M1) after curl installing 0.6.2 AMD64 build Jun 6, 2022
@ketang
Copy link
Contributor

ketang commented Jun 6, 2022

Was this on an M1 laptop? Or an Intel one?

@bpmct
Copy link
Member

bpmct commented Jun 6, 2022

This was an intel laptop, but I'm unable to reproduce

@bpmct
Copy link
Member

bpmct commented Jun 6, 2022

Mark and I debugged this a bit further. He was able to consistently reproduce when upgrading from 0.6.0 to 0.6.2. I was not able to reproduce.

One primary difference is he uses a MacOS Big Sur and I use Monterey. It seems like a reboot also serves the problem for him, but not new terminal sessions.

@kylecarbs kylecarbs changed the title Bug: coder gets zsh killed on macOS (not M1) after curl installing 0.6.2 AMD64 build Coder gets zsh killed on macOS (not M1) after curl installing 0.6.2 AMD64 build Jun 7, 2022
@ketang
Copy link
Contributor

ketang commented Jun 7, 2022

It's not great to say we only support the latest macOS, and it's likely going to be a few months before 13 comes out. I think we're going to need to tackle this one after initial shipment.

@sharkymark
Copy link
Contributor Author

sharkymark commented Jun 9, 2022

@bpmct My workaround (for now) is putting $HOME/.cache/coder in the path, since that is where we originally copy coder from. And then it works.

@bpmct bpmct self-assigned this Jun 9, 2022
@bpmct
Copy link
Member

bpmct commented Jun 9, 2022

This is probably a bug in how the copy works then. I'll debug

@bpmct
Copy link
Member

bpmct commented Jun 13, 2022

Will compare this to the helm install script and see if a permissions issue occurs: https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3

@bpmct
Copy link
Member

bpmct commented Jun 13, 2022

I believe this has to do with how Apple "trusts" binaries. Deleting the binary right before copying in the new one does the trick.

@misskniss misskniss added api Area: HTTP API site Area: frontend dashboard labels Jun 14, 2022
@misskniss misskniss added this to the Community MVP milestone Jun 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api Area: HTTP API site Area: frontend dashboard
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants