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> wrote:

> 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
_______________________________________________
DOMjudge-devel mailing list
DOMjudge-devel@domjudge.org
https://www.domjudge.org/mailman/listinfo/domjudge-devel