Hacker News Reader

Comment by jakecodes | Hacker News Reader

@sashk Thanks for the feedback. Your feedback, and others has been heard loud and clear and we've been hard at work this next month. For next month's release (9.4) we were able to tackle just about 100 UI polish bugs. New systems are being put into place to make sure we are polished right out the door, and that the UI is consistent. We want you to love our UI.

View on HN

Not sure if this has been added to the bug tracker, but when your creating a merge request, clicking the two branches and bringing up the selection boxes used to focus them so you could type into the search straight away. It no longer does, so it needs two extra clicks.

It's small stuff like this that is quite annoying. Great release though, especially with the container registry fixes.

Thanks for pointing this out. I opened a new issue about this; here https://gitlab.com/gitlab-org/gitlab-ce/issues/34246

I’d like to report a few issues with the docker containers you provide – currently they don’t run at all, because they claim to require privileged access to several things? It’s not ideal (I’m trying to run GitLab CE on kubernetes, but I’ll likely have to modify it myself anyway to add OIDC login)

Our Docker images source is stored in our omnibus repo [1]. We also have docs detailing the usage of our Docker images. [2]

[1] - https://gitlab.com/gitlab-org/omnibus-gitlab/tree/master/doc...

[2] - https://docs.gitlab.com/omnibus/docker/

Yes, I know. I’ve deployed them, and they crash. While following your full instructions. Because tzdata isn’t writable.

Hi Kuschku,

Thanks for the feedback. Our current Docker container does require root because it is based on our Omnibus packages.

We are working to create a set of lean containers, one for each GitLab service (Sidekiq, Unicorn, Gitaly, etc.), which will no longer require root access.

More details are available in the issue that is tracking this effort: https://gitlab.com/charts/charts.gitlab.io/issues/14

Ah, okay, thanks. That explains my issue with running it on kubernetes. I'll look at that issue.

Reply on news.ycombinator.com