Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitLab Container Registry

about.gitlab.com

Post reply on HN
Print view View original

71–80 of 121 posts

Re: GitLab Container Registry

#71

Post by moondev »

davexunit wrote: post #46
moondev wrote: post #35

Earlier quoted context omitted.

Don't you think that gitlab adding container registry support will encourage more people to build their own images, as opposed to trusting "black-box" images from elsewhere? Combining a base image with the deployable artifact is much more efficient than baking amis or other images. You then know exactly what your image contains and nothing more, because you built it yourself. Of course I'm looking at this from the pe…

Any nontrivial image relies on a large number of other images as a base, and just because you built it yourself doesn't mean that you didn't just download and install software with known security vulnerabilities.

The thought is you use a vanilla LTS image as a base. If that needs to updated then your ci can easily do it.

You then combine that with your installable artifact (deb, rpm). It's the same exact process using classic images, so i'm not sure what the complaint about docker specifically would be.

Re: GitLab Container Registry

#73

Post by nikolay »

andromeduck wrote: post #43
r3bl wrote: post #41

Earlier quoted context omitted.

I really don't know what to hope for. All that I do now that I really enjoy watching what looks like a full on feature battle between GitLab and GitHub going on at this moment. As a guy who uses both (GitLab for my job, GitHub personally), I feel like I'm getting the best of both worlds. Although , to be perfectly honest, it feels to me like, at this point of the "feature battle", GitLab started embracing and actuall…

now if only they could get gitlab.com page loads consistently under 1 second... x_x

Yup! It supposedly is written in a much more efficient language, but it severely slower than GitHub and Bitbucket.

Re: GitLab Container Registry

#74

Post by netcraft »

tmaczukin wrote: post #25
netcraft wrote: post #17

am I correct that this is only for on-prem deployments, that they aren't going to be offering a public container registry a la docker hub or quay?

You can enable Container Registry for your projects on GitLab.com :) And in a few days our shared runners should be updated to support the full docker workflow with the Container Registry.

thats really amazing - are there size limits?

Re: GitLab Container Registry

#75

Post by ymse »

nikolay wrote: post #73
andromeduck wrote: post #43

Earlier quoted context omitted.

now if only they could get gitlab.com page loads consistently under 1 second... x_x

Yup! It supposedly is written in a much more efficient language, but it severely slower than GitHub and Bitbucket.

It's written in Ruby like Github, but the latter have considerably more experience running high-traffic systems.

Just perused their job page and will apply this week. Sound like they could use some Varnish and Ceph talent :)

Re: GitLab Container Registry

#76

Post by nikolay »

ymse wrote: post #75
nikolay wrote: post #73

Earlier quoted context omitted.

Yup! It supposedly is written in a much more efficient language, but it severely slower than GitHub and Bitbucket.

It's written in Ruby like Github, but the latter have considerably more experience running high-traffic systems. Just perused their job page and will apply this week. Sound like they could use some Varnish and Ceph talent :)

Oh, I confused it with Gogs, sorry!

Re: GitLab Container Registry

#78

Post by radicalbyte »

sytse wrote: post #66
Cyph0n wrote: post #64

Earlier quoted context omitted.

Damn, you are one lucky person! Getting paid to work on OSS is a dream come true. Keep up the awesome work everyone :)

Thanks! And I think Connor created his own luck. People were assuming he already worked at GitLab since he was so active on social media and on our issue trackers. If you consistently contribute to GitLab it is very hard for us not to hire you.

It's such a crazy effective way to hire people. Luckily most companies don't understand it ;-)

Re: GitLab Container Registry

#79

Post by Tiksi »

sytse wrote: post #70
Tiksi wrote: post #31

It seems like every time I set up some supporting infrastructure it ends up rolled into the next gitlab release a week later, not that I'm complaining (much). If you haven't checked out gitlab in a while, you definitely should. It's been moving fast and come a long way lately. Thank you Gitlab team for making an open source, self hosted platform and all the recent improvements you've made.

Thanks for your kind words. May I ask what supporting infrastructure you'll set in 3 weeks from now? We'll have to add it to the schedule for 8.9

Well since you asked, I'm working on a system that writes perfect bug-free code for me, but if you can implement that I'll save myself the effort.

But really, the next thing on the roadmap is to get tighter integration between our CFM (saltstack/salt-api) and gitlab. Tie it into deploys, auto-open issues on failed states, etc., though that's gonna be more on the salt side than the gitlab side and likely wouldn't make sense for you guys to implement anyways.

Im sure I'll end up setting up whatever does make it into 8.9 a week before it's released though.

Re: GitLab Container Registry

#80

Post by Cyph0n »

sytse wrote: post #66
Cyph0n wrote: post #64

Earlier quoted context omitted.

Damn, you are one lucky person! Getting paid to work on OSS is a dream come true. Keep up the awesome work everyone :)

Thanks! And I think Connor created his own luck. People were assuming he already worked at GitLab since he was so active on social media and on our issue trackers. If you consistently contribute to GitLab it is very hard for us not to hire you.

That's a pretty effective hiring method in my opinion. You guys should publish a blog post or something on your hiring practices and results - I'm sure the HN crowd would enjoy it.
Post reply on HN