Containers not found after inginious docker-agent update

[vvandenschrieck]

After having updated my inginious instance last week, all codings problems where crashing because of "unavailable environment".
After some research, I believe this is related to the commit on INGInious issue #435 [UCL-INGI/INGInious/pull/435] : The label org.inginious.grading.agent_version is missing on the INGInious-containers and so they are not recognised by the inginious docker-agent anymore.

Manually adding the label to the dockerfile of my grading environment solved the issue in my case, but it would be nice to update the official docker images accordingly.

[sargreal]

The images seem to have been updated on the development tag.

It would however be really nice if the images were tagged based on this new agent-version (maybe with a -dev suffix until the version is final)

[anthonygego]

We are currently facing an issue with Docker Hub requiring all access (write access also) on all repos to work. We'll probably add the containers build instruction in the installation guide and disable the docker hub repos.

[ThaSami]

rebuild the images and put the tag manualy

[sargreal]

We are currently facing an issue with Docker Hub requiring all access (write access also) on all repos to work. We'll probably add the containers build instruction in the installation guide and disable the docker hub repos.

You can always just build the images in some ci-pipeline like Travis-CI and then push them to Docker Hub. I have created such a workflow with gitlab and have some of the Images now on DockerHub under unibasme/inginious-testing. The tags are the same name as the container name for better distinction.