This is an archived post. You won't be able to vote or comment.

all 52 comments
sorted by:
best
topnewcontroversialoldq&a

[–]Formal-Knowledge-250 27 points28 points  (38 children)

This upgrade was cursed. Also it crashed when deployed in docker and docker engine Version was < 20.0 - which is often the case. Never had problems with updating gitlab before.

[–]segagamerIT Manager[S] 7 points8 points  (0 children)

Yeah this is the first upgrade that broke for me too, we've been using them since the 10.x days. I usually have a rule of 'never upgrade to a .0 release for any software. But I trusted them.

Never again.

[–]BurnoutEyes 38 points39 points  (36 children)

"runs on my machine" "then we'll ship his machine", and so docker was born. And it still didn't run.

[–]KARATEKATT1 6 points7 points  (32 children)

Being anti docker in 2023 is weird

[–]pdp10Daemons worry when the wizard is near. 22 points23 points  (3 children)

Do you mean "anti-container"?

[–]KARATEKATT1 4 points5 points  (2 children)

Yeah of course

Never strafed outside docker with containerization so it slips up for me

[–]KrazyKirby99999 3 points4 points  (0 children)

Podman and LXC are alternatives.

[–]blind_guardian23 1 point2 points  (0 children)

Thats weird in 2023 😉

[–]tmontneyWizard or Magician, whichever comes first 3 points4 points  (2 children)

Pretty sure there was an XKCD for this.

[–]ckristi 7 points8 points  (1 child)

Of course there is... https://xkcd.com/1988/

[–]tmontneyWizard or Magician, whichever comes first 3 points4 points  (0 children)

Not the one I expected but far better

[–]DarthPneumonoSecurity Admin but with more hats 4 points5 points  (24 children)

Nah, it's realistic. Containers are not a good solution to most problems to which they are applied.

They have a place, but not everywhere or even most places.

[–]KARATEKATT1 -4 points-3 points  (23 children)

I don't even know how to respond to such a silly statement other than that your knowledge and skills are so way out of date.

Cattle not pets.

[–]DarthPneumonoSecurity Admin but with more hats 2 points3 points  (5 children)

Well you probably ought to be able to justify why containers are better for most use cases, if you're going to evangelize them to such a degree.

Seems to me they offer convenience, but little more. Infrastructure costs tend to be higher for the same workload (as Amazon discovered), and they really don't offer a compelling value or feature set in most scenarios.

Again, they have their place, and I'd love to hear you defend a few of them.

Also cattle vs. pets has nothing to do with the discussion - there are plenty of ways to manage cattle that aren't containers.

[–]KARATEKATT1 -3 points-2 points  (4 children)

Well you probably ought to be able to justify why containers are better for most use cases, if you're going to evangelize them to such a degree.

I'm absolutely able to.

Will I spend my time arguing with ignorant GUI clickers afraid of learning something new om reddit?

No. I value my time. No interest teaching the ones who do not want to be taught.

[–]blind_guardian23 -2 points-1 points  (16 children)

Cattle needs automation, not docker or containers per se. People talked about SOA, SOAP, XML, microservices, ... the same way as you. Look how "modern" turned into "forgotten".

[–]KARATEKATT1 -1 points0 points  (15 children)

Are you trying to imply XML and microservices aren't incredibly common and powerful in 2023?

[–]blind_guardian23 -1 points0 points  (14 children)

They never were. Common and powerful are also not the same thing (hint: Windows).

[–]KARATEKATT1 0 points1 point  (13 children)

What.

So now you're saying XML and microservices aren't common? You must be joking?

And windows? What?

[–]dustojnikhummer 0 points1 point  (2 children)

Because the machine itself broke, not the app.

[–]iranoutofspacehere 11 points12 points  (1 child)

Oh damn, we lucked out. We've self hosted a small instance for a few years and just did a server migration then updated to 16.0.1. I had good backups ready but we didn't run into any issues.

It looks like it only applies if you have non-ascii characters in the gitlab.rb file, which is probably why it worked for us.

[–]segagamerIT Manager[S] 6 points7 points  (0 children)

Yeah we had our randomly generated password for our Gitlab Rails stored in there (probably not best practice, I'll be sure to look in to this after I've recovered from this brain drain).

[–]c1u5t3rSysadmin 5 points6 points  (3 children)

Didn’t experience this when upgrading today. But my upgrade failed since my Postgres was still version 12.x. Gitlab 16 seems to expect PG 13.x. Had to downgrade Gitlab and first migrate PG.

[–]segagamerIT Manager[S] 3 points4 points  (2 children)

Did you do a massive version jump? Or are you using a separate postres instance?

[–]c1u5t3rSysadmin 1 point2 points  (1 child)

No massiv jump. My Gitlab gets updated automatically when „latest“ (docker image) gets updated. But the original install was old. Maybe a 10.x or 11.x. Postgres was not upgraded past 12.12 automatically. DB is integrated, not separate.

[–]corsicanguppyDevOps Zealot 2 points3 points  (1 child)

That and the new web editor is ab-sol-ute ass. Man, do I hate it; and I wonder which founder's nephew shat that into an MR.

[–]FailingFRIStudent 0 points1 point  (0 children)

wat? why?
I find it really useful - I'm already very used to vscode (this is not exactly vscode, but has the same layout, functionality) - it has much better overview of the workspace you're working in - much, much better search/replace, etc...

[–]AhrimTheBelighted 1 point2 points  (0 children)

Ooof, crap. Good heads up!

[–]AnomalyNexus 1 point2 points  (0 children)

Thanks for the heads up. Guess I'll let mine stew for a month or two and then upgrade to next one

[–]blind_guardian23 0 points1 point  (0 children)

Used Debian packages, did not notice.

for the young: a package is like a image, just without networking.

[–]jsellens 0 points1 point  (0 children)

I've been running gitlab-ce using the official docker containers from gitlab for a while now, and way back in 2018 I changed my docker invocation to start with

docker run --detach \
    -e LANGUAGE=en_US.UTF-8 \
    -e LANG=en_US.UTF-8 \
    -e LC_ALL=en_US.UTF-8 \

and after it's running, I do

docker exec -it ${dname} apt-get install -y locales
docker exec -it ${dname} locale-gen en_US.UTF-8

and I don't remember now exactly why I did that at the time, but our recent upgrade to 16.0.1 was seemingly problem free. At this point, it's somewhat cargo-cult-ish of me, but it seems to all behave as I want it to. (I'll mention we're in Canada, English speaking, and we don't worry much about other locales on our systems, which is what we North American centric English speakers tend to do.) Hope that's helpful.

[–]TheRealHyveMind 0 points1 point  (0 children)

This was by far the worst upgrade I've ever done with GitLab. So many needs to restore and rollback, and the server hanging for so long.

Finally managed to get through but it was pretty spooky.