Don't run test in debugger on Arm #4358
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CirrusCI moved the Arm infrastructure from AWS to Google's cloud. In the process, the security setup for Docker containers changed and we no longer have the permissions required to "debug C++ code" in containers on Arm. Cirrus is unable "for security reasons" to change the configuration of the GKE to accomodate our needs. The error in question happens when you try to run a program started up in the debugger. We get: "'A' packet returned an error: 8" According to a posting on StackOverflow, this can be addressed by adding "--cap-add=SYS_PTRACE --security-opt seccomp=unconfined" to the "docker run" command. According to CirrusCI they added NET_RAW and SYS_PTRACE capabilities in an attempt to address the problem. However, that didn't work as we continued to get errors. Cirrus says they would have to weaken the seccomp setting for their entire cluster to address, something they aren't comfortable doing. They said we could run the workloads in privileged containers on dedicated virtual machines. That is a decent amount of work to set up and administer and adds some additional overhead money-wise. If we really need to turn this back on, we could consider going down that route.
ponylang-main
added
the
discuss during sync
jemc
approved these changes
Jul 7, 2023
ponylang-main
removed
the
discuss during sync
This was referenced Jul 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CirrusCI moved the Arm infrastructure from AWS to Google's cloud. In the process, the security setup for Docker containers changed and we no longer have the permissions required to "debug C++ code" in containers on Arm.
Cirrus is unable "for security reasons" to change the configuration of the GKE to accomodate our needs.
The error in question happens when you try to run a program started up in the debugger. We get:
"'A' packet returned an error: 8"
According to a posting on StackOverflow, this can be addressed by adding "--cap-add=SYS_PTRACE --security-opt seccomp=unconfined" to the "docker run" command.
According to CirrusCI they added NET_RAW and SYS_PTRACE capabilities in an attempt to address the problem. However, that didn't work as we continued to get errors. Cirrus says they would have to weaken the seccomp setting for their entire cluster to address, something they aren't comfortable doing. They said we could run the workloads in privileged containers on dedicated virtual machines. That is a decent amount of work to set up and administer and adds some additional overhead money-wise. If we really need to turn this back on, we could consider going down that route.