testmycode / testmycode/tmc-server
tmc-sandbox: ptrace: Operation not permitted
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 51
- Forks
- 42
- Avg merge
- 1h 27m
- Merged PRs (30d)
- 1
Description
Getting Running the submission failed in Submission logs:
[0.400874] Checking that ptrace can change system call numbers...Core dump limits :
[0.400931] soft - NONE
[0.400944] hard - NONE
[0.401052] ptrace: Operation not permitted
[0.401247] check_ptrace : expected SIGSTOP, got status = 9
Changing tmc-sandbox capabilities in docker-compose-dev.yml:
cap_add:
- SYS_PTRACE
seems to fix the issue. Maybe the default capabilities have changed in the newer docker versions.
Platform:
Docker version 17.12.0-ce, build c97c6d6
docker-compose version 1.19.0, build 9e633ef
Linux hostname 4.9.0-5-amd64 #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) x86_64 GNU/Linux
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docker-compose-dev.yml and the tmc-sandbox configuration, then reproduce the submission failure using the reported Docker and Debian environment. Check how ptrace permissions are configured and verify the sandbox can pass the ptrace check without producing the logged error; document the confirmed configuration and any version-specific behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, linux
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100