Yannis Mazzer

Yes, here it is : ``` | NVIDIA-SMI 470.82.01 Driver Version: 470.82.01 CUDA Version: 11.4 | |-------------------------------+----------------------+----------------------+ | GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan...

@kpouget yes I have read this doc, but the return code 14 is not blocking workloads since it is just a warning, that is why I'm asking :)

Thanks for your support, I managed to make it work with a private build. Do you plan to make it working natively? should I make a pull request? @zvonkok I...

Hi, Just a little up, to check whether you can merge it?

Hi, We are facing the same issue. In addition to the reported details, the gitlab registry cleanup policy when enabled will generate plenty of logs in both sides due to...

Hi @sachilles, > unfortunately I've been using only the integration of the docker registry into GitLab as pointed out in https://github.com/sameersbn/docker-gitlab/blob/master/docs/container_registry.md#gitlab-container-registry. This is what we did, didn't you met the...

Hi @sachilles @avvertix, I just tried out the simple following procedure: - Starting from a `registry:2.8`, I replaced the image by the latest gitlab-registry `registry.gitlab.com/gitlab-org/build/cng/gitlab-container-registry:v3.88.0-gitlab` - I changed registry mounted...

Hi, Juste a little gentle reminder on this PR to know what is still required to merge?

Hi, I just updated the PR to work on top of `16.7.0`, this feature is quite important for gitlab instances migrated from other installation methods to `sameersbn/docker-gitlab` docker image. Could...

> Hi, > > I just updated the PR to work on top of `16.7.0`, this feature is quite important for gitlab instances migrated from other installation methods to `sameersbn/docker-gitlab`...