Can I use gitlab container registry with gitlab.com? Can I use private images in said registry with public gitlab.com ci builders?
I haven't found a way to use private containers with gitlab.com ci yet without spinning up a worker for every project.
Maybe a way to register a "team wide" builder?
GitLab Container Registry
101–110 of 121 posts
Re: GitLab Container Registry
#102Can I use gitlab container registry with gitlab.com? Can I use private images in said registry with public gitlab.com ci builders? I haven't found a way to use private containers with gitlab.com ci yet without spinning up a worker for every project. Maybe a way to register a "team wide" builder?
Currently not. The limitations can be found here: http://docs.gitlab.com/ce/container_registry/README.html#lim.... We plan to improve that in one of upcoming releases.
Re: GitLab Container Registry
#103Earlier quoted context omitted.
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.
Thanks, our hiring practices are detailed on https://about.gitlab.com/handbook/hiring/ what kinds of results should we include? I'm also thinking about writing about an open organization, where the handbooks and issue trackers are public. Would that be interesting?
Yeah, definitely. It's an interesting concept, I didn't know about the handbooks being public, seeing employees interacting on issues in the open and seeing the company's strategy be posted publicly is very cool.
Re: GitLab Container Registry
#104It's happening: GitLab has basically filled the feature gap with GitHub and it is surpassing it.
Once the performance gap closes it'll be even more exciting.
I just worry about 10, 15, 20 years in the future when ArchiveTeam has to back up GitHub and GitLab and whatever else... there's so much data!
Re: GitLab Container Registry
#105In the same idea, has someone already worked integration with a debian repository (with aptly or similar) and has some linked to share on how to do it the smartway? We're thinking about using FPM to create the debian package Package which is the retrieve as the artifacts of the gitlab-ci build stage And then to have a separate service that will receive a webhook at the end of the (successful) build, to retrieve the a…
At my work, we have a setup close to this. On a successful build of jenkins (after build action), a deb is generated with FPM (awesome piece of software btw) and uploaded to an s3 bucket. Then on another machine, a cron that run every minutes sync the s3 bucket to a local aptly repository and publish it to another s3 bucket which is the real debian repository. This works well but the s3+cron part is probably not the…
I know it probably doesn't matter too much for internal use, but what does Lintian say about your packages?
Re: GitLab Container Registry
#106Earlier 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.
At least by building images by myself I'm taking responsibility in a way for the security of them - rather than relying on the (in)security of whatever base image.
I did see a feature somewhere for scanning container images for security vulnerabilities, but I think something closer to FreeBSD's pkg-audit is needed.
Re: GitLab Container Registry
#107It's happening: GitLab has basically filled the feature gap with GitHub and it is surpassing it.
Once the performance gap closes it'll be even more exciting. I just worry about 10, 15, 20 years in the future when ArchiveTeam has to back up GitHub and GitLab and whatever else... there's so much data!
There will also be bigger storage :)
Re: GitLab Container Registry
#108These days it seems that Docker is everywhere. I am new to docker and I seem to find it as one more additional complicated system that the developer now needs to learn in order to deploy his or her application.
How useful do you find docker for application which can be deployed on Heroku or Beanstalk? I can understand using docker for a Language ecosystem which is not supported on Public PaaS. Or for people for whom public PaaS is not an option.
I would like to know about the experience of using Docker in day to day development from people who have used Docker in team environments. How was your experience of converting the team to use Docker instead of their regular development/deployment? For example, at our company, For LAMP or MEAN or Java Stacks, we have a defined a procedure of setting up the dev machines to include all these tools and developers know how to manage these on their own machine. Once the code is pushed to Jenkins, there are deploy scripts written by tech leads which take care of deployment to various servers or to Heroku.
In your Docker driven development process, did everybody started using docker on their development machine too? Or everybody just kept using their local setup, and only one/two people handled the task of creating final docker images? Or do you just use you CI server to handle the docker image creation and deployment from that point onwards?
Re: GitLab Container Registry
#109So awesome! I've been invested into the Docker ecosystem lately and one of the next things I've wanted to setup is a decent CI workflow. I wish Github would also ship more features at the pace Gitlab is. The only issue I've had with Gitlab are the response times on their UI. Hopefully they sort that out soon.
I suppose you are using GitLab.com. We're working on improving the speed [0]. If you are willing to run your own instance, it should be fast.
Re: GitLab Container Registry
#110I wish Gitlab had an easy clean way to import GitHub. The current method involves setting up oauth information in the config file and restarting gitlab. Not nice :/ I fail to see why they cannot just work with GitHub API tokens for import?