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

41–50 of 121 posts

Re: GitLab Container Registry

#41

Post by r3bl »

nikolay wrote: post #4

At this pace of innovation, GitHub will soon be a part of the history! GitHub has done a tremendous job with forking and pull requests, but, at least recently, they've acted disorientedly! I hope they get back into shape!

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 actually improving every single thing I liked about GitHub to the point where I'm questioning my stay on GitHub for personal projects.

Re: GitLab Container Registry

#43

Post by andromeduck »

r3bl wrote: post #41
nikolay wrote: post #4

At this pace of innovation, GitHub will soon be a part of the history! GitHub has done a tremendous job with forking and pull requests, but, at least recently, they've acted disorientedly! I hope they get back into shape!

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

Re: GitLab Container Registry

#44

Post by sytse »

rudedogg wrote: post #36
connorshea wrote: post #10

Kind of unrelated, but I'm super happy to be working at GitLab. Nearly everything we do is out in the open, and most features are available in CE, which is fully open source ( https://gitlab.com/gitlab-org/gitlab-ce ). I've wanted great, open source tools that don't look like dung for a long long time, and GitLab is definitely reaching that goal. Can't help but gush about the product we're building. :D Here are some…

I'm running GitLab CE off a NAS to host my projects, and it works really well. Thank you all for making it freely available.

Glad to hear that, thanks for using GitLab! For other people, I think there are Synology packages on https://www.synology.com/en-us/dsm/app_packages/Docker-GitLa...

Re: GitLab Container Registry

#45

Post by sytse »

yoavm wrote: post #40

Up until recently I never even considered using CI in my projects because I just didn't have the time. The way GitLab are implementing all these tools makes it not only easy to use, but fun.

Glad to hear that! This was our intention. CI and CD is something everyone knows they should do but it isn't always done. By making it easier to set up we try to get more people to do it and feel good about themselves.

Re: GitLab Container Registry

#46

Post by davexunit »

moondev wrote: post #35
davexunit wrote: post #33

Earlier quoted context omitted.

The problem is that Docker, and more generally using stacks of binary disk images, is fundamentally flawed with respect to security and reproducibility. It's nontrivial to inspect these images for vulnerabilities because there is nothing that specifies the precise set of software that is in that image. Some stuff is compiled from source, some stuff is installed via one or more package managers, each of which may bund…

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.

Re: GitLab Container Registry

#47

Post by sytse »

diggan wrote: post #38
diggan wrote: post #14

I'm excited for this, seems like GitLab is moving more into a all-in-one solution, compared to Github that focuses on "social coding", whatever that now means. So to try out this new feature (together with the pipelines), I tried setting up a simple project that uses a docker image to serve a simple html page. However, it seems like it's not possible to build/push from the CI system (unless you setup a self-hosted ru…

Ah, thanks to sytse, Snappy and tmaczukin for the replis. I missed that. My configuration looks like this currently (and I'm guessing I'll hold of for a few days for the shared workers to get updated): image: docker:latest services: - docker:dind stages: - build - deploy build: stage: build script: - docker build -t registry.gitlab.com/victorbjelkholm/deploy-html-test:latest . only: - master deploy: stage: deploy scr…

Thanks, you didn't miss anything in the blog post, we updated the blog post. https://gitlab.com/gitlab-com/www-gitlab-com/commit/c758f6b2...

Re: GitLab Container Registry

#48

Post by sytse »

Snappy wrote: post #24
diggan wrote: post #14

I'm excited for this, seems like GitLab is moving more into a all-in-one solution, compared to Github that focuses on "social coding", whatever that now means. So to try out this new feature (together with the pipelines), I tried setting up a simple project that uses a docker image to serve a simple html page. However, it seems like it's not possible to build/push from the CI system (unless you setup a self-hosted ru…

Yeah, sorry about that. We'll update the blog post to clarify. We're updating the CI runners this week to support this.

Updated with https://gitlab.com/gitlab-com/www-gitlab-com/commit/c758f6b2...

Re: GitLab Container Registry

#50

Post by sytse »

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

Yes, we should fix the slow page loads on GitLab.com. We're working on it in https://gitlab.com/gitlab-com/operations/issues/42 I'm sorry for the current slowness.
Post reply on HN