Thread

SO
Shubham Oulkar2:41 PMOpen in Slack
Hi 👋 today tried spinning up Archestra using GitHub Codespaces ran into a boot failure and endup on Recovery Mode workspace. After digging into the logs, it looks like the current .devcontainer configuration crashes due to iptables permission issues and zsh-in-docker build failures in the cloud environment. I’ve managed to get a working fix locally, but I wanted to ask the maintainers about the intended direction for the DevContainer.
I'm happy to submit a PR with the fix once I know which approach fits the project's goals better!

6 replies
MK
Matvey Kukuy (archestra team)7:43 PMOpen in Slack
Hi! That's a great finding, I'm personally very optimistic about making sure that Archestra is able to run in as many dev envs as possible, so would appreciate the PR!
👏1
SO
Shubham Oulkar3:49 AMOpen in Slack
Great I am taking this as my 1st contribution to the project.
SO
Shubham Oulkar3:49 AMOpen in Slack
❤️
SO
Shubham Oulkar3:52 AMOpen in Slack
I will share all the details in github issue.
🙌2
SO
Shubham Oulkar6:45 PMOpen in Slack
hi @user issue is open https://github.com/archestra-ai/archestra/issues/4422 Should I wait for issue assign?
MK
Matvey Kukuy (archestra team)11:18 AMOpen in Slack
@user, we have a responsible ai policy. Your issue is clearly AI-generated. I will close.
👀1😞1