Open qn06142 opened 2 months ago
Can you provide us with a minimal set of test and solution code for your problem so we can reproduce it?
--
@minhnhatnoe can you take a look at this? exit code 2
sounds like some missing command (isolate?)
Can you provide us with a minimal set of test and solution code for your problem so we can reproduce it?
--
@minhnhatnoe can you take a look at this?
exit code 2
sounds like some missing command (isolate?)
I used the tests from this database: https://github.com/natsukagami/kjudge/files/4826816/kjudge.db.zip Also, I tried this set of tests, and solution, before trying the above db: https://drive.google.com/file/d/1xaVpZtQk6cZk3QJwjdRKGuy-zHObVYB5/view?usp=sharing https://drive.google.com/file/d/1dv7arAnMO0iOIV1VwArtDuaGQ7r-JH7b/view?usp=sharing (note: the two files were taken from free contest)
Thanks!
A little update: I forgot to shutdown the server, the jobs are still coming in...
That's fine, jobs re-queue themselves on failure :)
I'll take a look later today
@qn06142 could you please send me the output of the command mount -v | grep cgroup
on your host system (the system running the Docker daemon)? This might be due to your system running Control Groups v2, which support is currently being added in https://github.com/natsukagami/kjudge/pull/112
mount -v | grep cgroup
It is indeed cgroups2, the command output is:
wheatley@wheatley-OptiPlex-7010:~$ mount -v | grep cgroup
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
side note: are there any quick workarounds? I am only using this for myself or people I trust, so sandbox is not needed.
@qn06142 with #112 merged, perhaps running the unstable
branch would work, please try it out; we probably still have to iron it out before putting out a tagged released though.
@qn06142 with #112 merged, perhaps running the
unstable
branch would work, please try it out; we probably still have to iron it out before putting out a tagged released though.
alright, trying that out right now, thanks :3
yup, using this:
sudo docker run --privileged -d --rm --name kjudge --volume=kjudge:/data -p 8080:80 -e ADMIN_KEY=secret natsukagami/kjudge:unstable
jobs now finish normally, for some reason the version is still stuck on 0.7.4, though
That's fine ^^
Should I close the issue or keep it open until 0.8.0 comes around?
Let's keep it open, we'll close it once we release 0.8. Thanks!
Thanks for helping too ^_^
Version: Latest version from docker Version string grabbed from page: 0.7.4 "Maaya Awatsuki" Bug: On submission, jobs fails with "exit code 2" some logs:
docker command:
sudo docker run --privileged -d --rm --name kjudge --volume=kjudge:/data -p 8080:80 -e ADMIN_KEY=supersecret natsukagami/kjudge:latest
behavior: Make a contest. Add some problems Submit code for any problem Wait forever for submission to be judged