-
Notifications
You must be signed in to change notification settings - Fork 255
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
Error when run docker #905
Comments
What are the contents of
replacing |
The image show that your container has been exited, you should start the container before running the |
I started the container and here's the result |
you should use |
thanks, here's the result
|
Weird, I think you should rebuild the image without cache. In cd tier1 && docker build --no-cache --build-arg TAG="master" -t dmoj/judge-tier1 -t dmoj/judge-tier1:latest . |
Also, please provide logs after running the command @leduythuccs mentioned. What I suspect happened is the judge entirely failed to autoconf, and generated a valid-but-empty YAML that we butchered by adding |
|
That's the error. Either upgrade your kernel (4.4 is very old!), or use https://github.com/DMOJ/judge-server/releases/tag/v3.0.2, as that is the last version that supports kernels before 4.8. |
I've just checkout branch 5fddf1d for vesion 3.0.2
The contents of judge-runtime-paths.yml is:
But there're the same errors when I run the command |
Please post the full logs of the build step when building without cache. If you still see
You are doing something wrong, as that message was added in 2ec9acd (which came after v3.0.2 / the commit you linked).
Ubuntu 16.04 is very old, and its 4.4 kernel is missing features that DMOJ requires to function properly. It's probably a good idea to upgrade at least the kernel: the sandboxing overhead is substantially lower on kernels supporting seccomp. Separately, we have very limited manpower to support configurations other than what we run in prod on https://dmoj.ca -- which is always the latest Debian, currently Debian 11. We're happy when other configurations happen to work, but that's all we can actually commit to supporting. |
Okay, thanks for your supports. |
I got the same problem but on linux kernel 4.18, centos 8.4. The contents of judge-runtime-paths.yml is right. `Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
!!
!! Installed /judge Using /env/lib/python3.11/site-packages Using /env/lib/python3.11/site-packages Using /env/lib/python3.11/site-packages Using /env/lib/python3.11/site-packages Using /env/lib/python3.11/site-packages Using /env/lib/python3.11/site-packages Auto-configuring BF: Failed to find "llc" ptrace: Operation not permitted Auto-configuring CBL: Failed to find "cobc" ptrace: Operation not permitted ptrace: Operation not permitted ptrace: Operation not permitted ptrace: Operation not permitted Auto-configuring D: Failed to find "dmd" ptrace: Operation not permitted Auto-configuring GASARM: Unable to natively debug ptrace: Operation not permitted Auto-configuring PHP: Failed to find "php" ptrace: Operation not permitted Auto-configuring PYPY: Failed to find "pypy" Auto-configuring SWIFT: Failed to find "swiftc" Auto-configuring TUR: Failed to find "tprolog" Any suggestion? |
error when run
docker run \ -v /mnt/problems:/problems \ --cap-add=SYS_PTRACE \ dmoj/judge-tier1:latest \ cli -c /problems/judge.yml
error is
The text was updated successfully, but these errors were encountered: