Error running abctl local install on Mac

Slack Knowledge Base Q&A API, Terraform and Other Topics
, , , ,
1

Summary

The user encountered a runtime error while trying to run ‘abctl local install’ command on a Mac. The error suggests a segmentation violation. The user is considering downgrading to a version prior to v0.5.0 as suggested by kapa.ai bot. They are seeking guidance on whether downgrading is the correct fix and how to proceed with it.


Question

Hi <#C021JANJ6TY|ask-community-for-troubleshooting>,

I am trying to set up and run the abctl install for the first time on a Mac. I received an error trying to run abctl local install command for the first time. What can I do to correct this issue? The http://kapa.ai|kapa.ai bot suggested downgrading to a version prior to v0.5.0. Is there something I need to correct or is downgrading in fact the correct fix? If so, how would I go about downgrading and what version should I use?

Version Info

macOS Sonoma: 14.5
Docker Desktop: 4.32.0
Docker: 27.0.3
abctl: 0.8.0

Error:

[signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0xb8d2c36]

goroutine 1 [running]:
github.com/airbytehq/abctl/internal/cmd/local.portAvailable.func1()
	github.com/airbytehq/abctl/internal/cmd/local/check.go:86 +0x16
github.com/airbytehq/abctl/internal/cmd/local.portAvailable({0xc17e980, 0xc0005a2aa0}, 0x1f40)
	github.com/airbytehq/abctl/internal/cmd/local/check.go:90 +0x37f
github.com/airbytehq/abctl/internal/cmd/local.NewCmdInstall.func1(0xc00042af08, {0xb8d8ddc?, 0x4?, 0xb8d8dc0?})
	github.com/airbytehq/abctl/internal/cmd/local/local_install.go:66 +0x36e
github.com/spf13/cobra.(*Command).execute(0xc00042af08, {0xd2dbc60, 0x0, 0x0})
	github.com/spf13/cobra@v1.8.0/command.go:968 +0xa44
github.com/spf13/cobra.(*Command).ExecuteC(0xc00042a608)
	github.com/spf13/cobra@v1.8.0/command.go:1115 +0x3ff
github.com/spf13/cobra.(*Command).Execute(...)
	github.com/spf13/cobra@v1.8.0/command.go:1039
github.com/spf13/cobra.(*Command).ExecuteContext(...)
	github.com/spf13/cobra@v1.8.0/command.go:1032
github.com/airbytehq/abctl/internal/cmd.Execute({0xc17e980?, 0xc0005a2aa0?}, 0x77359400?)
	github.com/airbytehq/abctl/internal/cmd/cmd.go:41 +0x4f
main.main()
	github.com/airbytehq/abctl/main.go:45 +0x1a7```
<https://airbytehq.slack.com/archives/C01AHCD885S/p1721316390407279>

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1721318990804449) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["abctl", "local-install", "mac", "error", "downgrade", "segmentation-violation"]
</sub>
2

Hey Jake, sorry you ran into this. I will have the team take a look at this issue today and see if we can get a fix out for you.

3

We have identified the bug, a fix is out here: https://github.com/airbytehq/abctl/pull/52#pullrequestreview-2186697720 Once that is merged, we will cut a new release with the fix.

4

<@U07C8CCC68Y> Thanks for the reply. Is there a timeline for when the new release will be cut? Do you release on a defined cadence?

I was able to move past this specific issue by passing a different port using the --port=? flag to the abctl local install command with help from <@U03U8FSJ8PK>.

Unfortunately I am getting another error now:

  ERROR   unable to create kind cluster: command "docker run --name airbyte-abctl-control-plane --hostname airbyte-abctl-control-plane --label io.x-k8s.kind.role=control-plane --privileged --security-opt seccomp=unconfined --security-opt apparmor=unconfined --tmpfs /tmp --tmpfs /run --volume /var --volume /lib/modules:/lib/modules:ro -e KIND_EXPERIMENTAL_CONTAINERD_SNAPSHOTTER --detach --tty --label io.x-k8s.kind.cluster=airbyte-abctl --net kind --restart=on-failure:1 --init=false --cgroupns=private --volume=/Users/jakeduckworth/.airbyte/abctl/data:/var/local-path-provisioner --publish=0.0.0.0:9000:80/TCP --publish=127.0.0.1:53968:6443/TCP -e KUBECONFIG=/etc/kubernetes/admin.conf kindest/node:v1.29.4@sha256:3abb816a5b1061fb15c6e9e60856ec40d56b7b52bcea5f5f1350bc6e2320b6f8" failed with error: exit status 126```
5

Probably today, tomorrow at the latest

6

<@U07C8CCC68Y> I just wanted to follow up on this issue. Upgrading to v0.8.1 fixed the initial SIGSEGV: segmentation violation bug I had.