Thanks Nicky. I haven't done a lot of docker, but I think I have everything set up right... except that I have crashing judgehosts when they try to compile a java program. Is there anything special I need to do when initializing the docker container? Thanks, Matt [Jan 23 20:28:27.579] judgedaemon[36]: No submissions in queue (for endpoint default), waiting... [Jan 23 20:36:52.350] judgedaemon[36]: Judging submission s1 (endpoint default) (t3/p23/java), id j1... [Jan 23 20:36:52.350] judgedaemon[36]: API request GET config [Jan 23 20:36:52.494] judgedaemon[36]: API request GET config [Jan 23 20:36:52.611] judgedaemon[36]: API request GET config [Jan 23 20:36:52.728] judgedaemon[36]: API request GET config [Jan 23 20:36:52.844] judgedaemon[36]: API request GET config [Jan 23 20:36:52.953] judgedaemon[36]: Working directory: /opt/domjudge/judgehost/judgings/judgedaemon-0-0/endpoint-default/c4-s1-j1 [Jan 23 20:36:52.970] judgedaemon[36]: API request GET submission_files [Jan 23 20:36:53.088] judgedaemon[36]: Fetching new executable 'java_javac_detect' [Jan 23 20:36:53.117] judgedaemon[36]: API request GET executable [Jan 23 20:36:53.240] judgedaemon[36]: Unzipping [Jan 23 20:36:53.290] judgedaemon[36]: Compiling [Jan 23 20:36:55.634] compile.sh[68]: starting '/opt/domjudge/judgehost/lib/judge/compile.sh', PID = 68 [Jan 23 20:36:55.637] compile.sh[68]: arguments: '/opt/domjudge/judgehost/judgings/judgedaemon-0-0/endpoint-default/executable/java_javac_detect/run' '/opt/domjudge/judgehost/judgings/judgedaemon-0-0/endpoint-default/c4-s1-j1' [Jan 23 20:36:55.640] compile.sh[68]: source file(s): Test.java [Jan 23 20:36:55.650] compile.sh[68]: starting compile [Jan 23 20:36:55.671] compile.sh[68]: checking compilation exit-status [Jan 23 20:36:55.675] compile.sh[68]: exiting, code = '101' [Jan 23 20:36:55.680] judgedaemon[36]: Running compile.sh caused a runguard error/crash: 'runguard error - 50029 - creating cgroup' -------------------------------------------------------------------------------- Compiling failed with exitcode 255, compiler output: /opt/domjudge/judgehost/bin/runguard: creating cgroup: Unknown error 50029 Try `/opt/domjudge/judgehost/bin/runguard --help' for more information. Error: failed to set /sys/fs/cgroup/memory/domjudge/dj_cgroup_97_1548272215/memory.memsw.limit_in_bytes: Cgroup, requested group parameter does not exist On Tue, Jan 22, 2019 at 6:29 AM Nicky Gerritsen <nickygerritsen@me.com> wrote:

Hi Matt,

The reason we do not have a recent Live Image is because we also do not have any recent Debian packages, which are used for the live image. I am not sure if it is easy to create new Debian packages, as 6.x changed our structure internally quite a bit and I expect the packaging to break.

If you need a fast way to set up DOMjudge, you can also use our new Docker images, which are up to date. See https://hub.docker.com/r/domjudge/domserver and https://hub.docker.com/r/domjudge/judgehost for this. If you only need a judgehost you can use the latter.

Nicky

On 22 Jan 2019, at 12:47, Matthew Fahrenbacher <matfah@d219.org> wrote:

Hi all. So I'm almost done with my next contest, but I see that the Live Images haven't been updated in about a year, so the version of the judgehost on the Live Image won't match with the latest release of the domjudge server. (I tried the most recent Live Image, and it didn't want to boot, even though older ones would).

I'm about to go through the process of building one myself following the directions here <https://github.com/DOMjudge/domjudge-packaging/blob/master/live-image/files/README>, but I wanted to check first to see if a prebuilt one was going to be created in the near future to save me the hassle.

Thanks! Matt Fahrenbacher Niles West High School _______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel

Got it! Thanks, Matt On Wed, Jan 23, 2019 at 1:49 PM Nicky Gerritsen <nickygerritsen@me.com> wrote:

Hi Matt,

You probably need to enable some grub CLI things on your host machine. See these steps in our code:

https://github.com/DOMjudge/domjudge/blob/master/misc-tools/create_cgroups.i...

If you are not on a Debian-based Linux OS, it might be a bit different, but it should be somewhat similar.

Hope this helps!

Nicky

On 23 Jan 2019, at 20:46, Matthew Fahrenbacher <matfah@d219.org> wrote:

Thanks Nicky. I haven't done a lot of docker, but I think I have everything set up right... except that I have crashing judgehosts when they try to compile a java program. Is there anything special I need to do when initializing the docker container?

Thanks, Matt

[Jan 23 20:28:27.579] judgedaemon[36]: No submissions in queue (for endpoint default), waiting... [Jan 23 20:36:52.350] judgedaemon[36]: Judging submission s1 (endpoint default) (t3/p23/java), id j1... [Jan 23 20:36:52.350] judgedaemon[36]: API request GET config [Jan 23 20:36:52.494] judgedaemon[36]: API request GET config [Jan 23 20:36:52.611] judgedaemon[36]: API request GET config [Jan 23 20:36:52.728] judgedaemon[36]: API request GET config [Jan 23 20:36:52.844] judgedaemon[36]: API request GET config [Jan 23 20:36:52.953] judgedaemon[36]: Working directory: /opt/domjudge/judgehost/judgings/judgedaemon-0-0/endpoint-default/c4-s1-j1 [Jan 23 20:36:52.970] judgedaemon[36]: API request GET submission_files [Jan 23 20:36:53.088] judgedaemon[36]: Fetching new executable 'java_javac_detect' [Jan 23 20:36:53.117] judgedaemon[36]: API request GET executable [Jan 23 20:36:53.240] judgedaemon[36]: Unzipping [Jan 23 20:36:53.290] judgedaemon[36]: Compiling [Jan 23 20:36:55.634] compile.sh[68]: starting '/opt/domjudge/judgehost/lib/judge/compile.sh', PID = 68 [Jan 23 20:36:55.637] compile.sh[68]: arguments: '/opt/domjudge/judgehost/judgings/judgedaemon-0-0/endpoint-default/executable/java_javac_detect/run' '/opt/domjudge/judgehost/judgings/judgedaemon-0-0/endpoint-default/c4-s1-j1' [Jan 23 20:36:55.640] compile.sh[68]: source file(s): Test.java [Jan 23 20:36:55.650] compile.sh[68]: starting compile [Jan 23 20:36:55.671] compile.sh[68]: checking compilation exit-status [Jan 23 20:36:55.675] compile.sh[68]: exiting, code = '101' [Jan 23 20:36:55.680] judgedaemon[36]: Running compile.sh caused a runguard error/crash: 'runguard error - 50029 - creating cgroup'

--------------------------------------------------------------------------------

Compiling failed with exitcode 255, compiler output: /opt/domjudge/judgehost/bin/runguard: creating cgroup: Unknown error 50029 Try `/opt/domjudge/judgehost/bin/runguard --help' for more information. Error: failed to set /sys/fs/cgroup/memory/domjudge/dj_cgroup_97_1548272215/memory.memsw.limit_in_bytes: Cgroup, requested group parameter does not exist

On Tue, Jan 22, 2019 at 6:29 AM Nicky Gerritsen <nickygerritsen@me.com> wrote:

...

Hi Matt,

The reason we do not have a recent Live Image is because we also do not have any recent Debian packages, which are used for the live image. I am not sure if it is easy to create new Debian packages, as 6.x changed our structure internally quite a bit and I expect the packaging to break.

If you need a fast way to set up DOMjudge, you can also use our new Docker images, which are up to date. See https://hub.docker.com/r/domjudge/domserver and https://hub.docker.com/r/domjudge/judgehost for this. If you only need a judgehost you can use the latter.

Nicky

On 22 Jan 2019, at 12:47, Matthew Fahrenbacher <matfah@d219.org> wrote:

Hi all. So I'm almost done with my next contest, but I see that the Live Images haven't been updated in about a year, so the version of the judgehost on the Live Image won't match with the latest release of the domjudge server. (I tried the most recent Live Image, and it didn't want to boot, even though older ones would).

I'm about to go through the process of building one myself following the directions here <https://github.com/DOMjudge/domjudge-packaging/blob/master/live-image/files/README>, but I wanted to check first to see if a prebuilt one was going to be created in the near future to save me the hassle.

Thanks! Matt Fahrenbacher Niles West High School _______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org https://www.domjudge.org/mailman/listinfo/domjudge-devel

On 23 Jan 2019, at 21:40, Thijs Kinkhorst <thijs@kinkhorst.com> wrote:

On Tue, January 22, 2019 13:29, Nicky Gerritsen wrote:

...

The reason we do not have a recent Live Image is because we also do not have any recent Debian packages, which are used for the live image. I am not sure if it is easy to create new Debian packages, as 6.x changed our structure internally quite a bit and I expect the packaging to break.

Probably it’s not too hard to get the Debian packaging back into shape. And probably we should do that. For 6.0 this is probably hard, because the debian package uses FHS and that was broken with the Symfony move. as it did a lot of relative path checks that shouldn’t be there. It should / might work better with master / upcoming 6.1

But besides that, I’m not sure we should continue to maintain both the live image and the docker containers. Their usecase seems rather similar and given that our time is limited I can imagine that we’d keep only one way of doing this instead of investig the effort in both systems.

What do you think? Good question. I’m not sure how much effort the live image is. The Docker containers are as easy as running “./build 6.0.4” and doing two "docker push”-es. I’m also not sure how many people actually use the live image. It seemed that at least Matt didn’t have to much of a problem to set up the Docker containers, even he hasn’t “done a lot of Docker”, so they seem to be pretty easy to set up. If the live image is not used that much, I’m not opposed to drop it.

Nicky

Machines with only a small amount of RAM that you don’t want to overwrite the OS of do sound like an interesting scenario for a live CD. Of course if we have Debian packages again for 6.x it is also quite easy for someone to just download a default Debian / Ubuntu live CD and install these packages onto them... Nicky

On 23 Jan 2019, at 21:53, Matthew Fahrenbacher <matfah@d219.org> wrote:

So for full disclosure, it's not working *exactly* how I liked it. I liked being able to install the image on a usb drive, plug it into a computer, and boot it up. But that's because the programming competition I help host is at a different location every year. The "success" I am having now is running domjudge through docker installed on Ubuntu running in VirtualBox... which is okay, but now I need to make sure that the host site will allow me to install VirtualBox on their machines. I tried running domjudge through docker on a Rancheros livecd, but you have to have more than 4 gigs of ram for that to work with the size of the containers (which my host site *might* have). I remember having crashing issues a few years back when I tried to run everything through virtual machines (judgehosts would die randomly), but that might be resolved now. I have no idea how many people are in the same boat I am.

Just my 2 cents! Matt

On Wed, Jan 23, 2019 at 2:45 PM Nicky Gerritsen <nickygerritsen@me.com <mailto:nickygerritsen@me.com>> wrote:

...

On 23 Jan 2019, at 21:40, Thijs Kinkhorst <thijs@kinkhorst.com <mailto:thijs@kinkhorst.com>> wrote:

On Tue, January 22, 2019 13:29, Nicky Gerritsen wrote:

...

The reason we do not have a recent Live Image is because we also do not have any recent Debian packages, which are used for the live image. I am not sure if it is easy to create new Debian packages, as 6.x changed our structure internally quite a bit and I expect the packaging to break.

Probably it’s not too hard to get the Debian packaging back into shape. And probably we should do that. For 6.0 this is probably hard, because the debian package uses FHS and that was broken with the Symfony move. as it did a lot of relative path checks that shouldn’t be there. It should / might work better with master / upcoming 6.1

But besides that, I’m not sure we should continue to maintain both the live image and the docker containers. Their usecase seems rather similar and given that our time is limited I can imagine that we’d keep only one way of doing this instead of investig the effort in both systems.

What do you think? Good question. I’m not sure how much effort the live image is. The Docker containers are as easy as running “./build 6.0.4” and doing two "docker push”-es. I’m also not sure how many people actually use the live image. It seemed that at least Matt didn’t have to much of a problem to set up the Docker containers, even he hasn’t “done a lot of Docker”, so they seem to be pretty easy to set up. If the live image is not used that much, I’m not opposed to drop it.

Nicky _______________________________________________ DOMjudge-devel mailing list DOMjudge-devel@domjudge.org <mailto:DOMjudge-devel@domjudge.org> https://www.domjudge.org/mailman/listinfo/domjudge-devel <https://www.domjudge.org/mailman/listinfo/domjudge-devel>