docker-gitlab: Build 17.6.0 timed out

CI build for 17.6.0 seems to have timed out and 17.6.0 is not available on dockerhub. Please run the task again.

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Reactions: 1
  • Comments: 34 (20 by maintainers)

Most upvoted comments

Fair enough. In the meanwhile, if anybody needs this very image built to 17.6.0 up to 17.6.2 I forked it, built them and published on the dockerhub here.

I’m working on a multistage Dockerfile. Using BuildKit (docker buildx build or DOCKER_BUILDKIT=1 docker build), which allows parallel execution of stages I could save around 5 minutes.

You can find an image for testing the multistage build at https://hub.docker.com/th2021/docker-gitlab The corresponding github repo is at https://github.com/th-2021/docker-gitlab/ multistage branch The image has amd64 and arm64 flavors

@fidoedidoe The image might be bigger because some caches and other intermediate files are not deleted. The new ENV/ARG variables are moved from install.sh to Dockerfile.multistage. So yes they are new wrt docker.

The offiziellen image doesn’t support relative url, e.g. /gitlab

Am 9. Januar 2025 19:18:23 MEZ schrieb suchwerk @.***>:

First, thank you for maintaining this project over the years! I’ve been using sameersbn/docker-gitlab for quite some time now and have been very happy with its flexibility and modularity. However, I recently started revisiting my deployment choices and noticed that the official GitLab Docker image has come a long way since I first chose this project. I’d like to ask the community and maintainers for some guidance:

What are the key advantages of continuing to use sameersbn/docker-gitlab today?

Does this project still offer unique benefits that make it a better choice for long-term deployments? Are there scenarios where this setup outperforms the official GitLab image in terms of flexibility, resource usage, or integrations? For example, are there significant benefits in terms of updates, security, or feature parity that the official image provides?

I appreciate the hard work that has gone into this project and understand it has been a great solution for many users, myself included. I’d love to hear thoughts from the maintainers and community on how sameersbn/docker-gitlab fits into the current GitLab Docker landscape and whether sticking with this setup remains a good long-term strategy.

– Reply to this email directly or view it on GitHub: https://github.com/sameersbn/docker-gitlab/issues/3042#issuecomment-2580972432 You are receiving this because you were mentioned.

Message ID: @.***>

The image should be th2021/docker-gitlabAm 09.01.2025 18:23 schrieb Gavin Fowler @.***>:

I got 404 for https://hub.docker.com/th2021/docker-gitlab correction: https://hub.docker.com/r/th2021/docker-gitlab

@th-2021 - I also get the 404 for the provided docker image url

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

I’m sure many here are watching this thread and thinking: Your collective efforts are very much appreciated!! I cannot help with the build process (beyond my pay grade), but if you guys would like some end-user testing when images are available (against existing known to be working non prod instance - aka version upgrade testing) I’m pretty sure I can dedicate some time to testing (only as/when you’re ready / needing).

Hi @fidoedidoe — if you want to test something, my repo should be public at https://gitlab.fami.ga/misc/docker-gitlab. This is currently running the 17.6.2 version I built, but I also have a branch with the 17.7.0 version I I managed to cleanly build after some woes, available in the corresponding Container Registry.

AFAIK all the build logs are also public (correct me if I am wrong), so you should be able to convince yourself that I did not do some sneaky shenanigans. Or you can also clone and build yourself if you want 17.6.2 and it’s fixes.

@tDo If necessary, we should do so. I would like to get permission from all maintainers (with respect) if possible, but if we can’t contact them, there is nothing we can do.
Stalled project are one of my greatest fears, and the confusion that would result from moving namespaces is a minor pain compared to that.

However, I am still just a contributor (the most active - at least in terms of commits - except for the maintainer) and do not have (nor will I have) any decision-making authority.

So what I’m trying to say is that I’m asking for more human resources with administrative privileges that can respond to emergencies.