Using Gitlab's Free Docker Registry

Daily short news for you

Privacy Guides is a non-profit project aimed at providing users with insights into privacy rights, while also recommending best practices or tools to help reclaim privacy in the world of the Internet.

There are many great articles here, and I will take the example of three concepts that are often confused or misrepresented: Privacy, Security, and Anonymity. While many people who oppose privacy argue that a person does not need privacy if they have 'nothing to hide.' 'This is a dangerous misconception, as it creates the impression that those who demand privacy must be deviant, criminal, or wrongdoers.' - Why Privacy Matters.

» Read more
There is a wonderful place to learn, or if you're stuck in the thought that there's nothing left to learn, then the comments over at Hacker News are just for you.

Y Combinator - the company behind Hacker News focuses on venture capital investments for startups in Silicon Valley, so it’s no surprise that there are many brilliant minds commenting here. But their casual discussions provide us with keywords that can open up many new insights.

Don't believe it? Just scroll a bit, click on a post that matches your interests, check out the comments, and don’t forget to grab a cup of coffee next to you ☕️

» Read more
Just got played by my buddy Turso. The server suddenly crashed, and checking the logs revealed a lot of errors:

Operation was blocked LibsqlError: PROXY_ERROR: error executing a request on the primary
Suspicious, I went to the Turso admin panel and saw the statistics showing that I had executed over 500 million write commands!? At that moment, I was like, "What the heck? Am I being DDoSed? But there's no way I could have written 500 million."

Turso offers users free monthly limits of 1 billion read requests and 25 million write requests, yet I had written over 500 million. Does that seem unreasonable to everyone? 😆. But the server was down, and should I really spend money to get it back online? Roughly calculating, 500M would cost about $500.

After that, I went to the Discord channel seeking help, and very quickly someone came in to assist me, and just a few minutes later they informed me that the error was on their side and had restored the service for me. Truly, in the midst of misfortune, there’s good fortune; what I love most about this service is the quick support like this 🙏

» Read more

The Problem

Are you using Docker in any of your projects? If so, you must have encountered the need to store and share images. The default Docker Registry limits the number of private images you can have. This means that if you have multiple projects, you have to make these images public, which compromises the privacy of your projects.

Normally, some people choose to pay for Docker to get more private images. Others prefer to set up their own registry to store internal images. Docker provides an open-source solution for creating your registry. For more details, see the Docker Registry.

If you are an individual user and can't afford a paid service or don't have resources to set up your own registry, then this article is for you. Gitlab currently offers a completely free registry, all you need is a Gitlab account.

Usage

Gitlab's registry is tied to a repository. This means that to use it, you need to create repositories first. Images will be associated with repositories, and you can store them by pushing Docker images with the same name as the repository to Gitlab.

To use Gitlab's registry, follow these steps:

Step 1: Generate an Access Token by going to Profile > Preferences > Access Tokens. Enter a name for the token and make sure to select the "read & write registry" permission.

After successfully generating the token, save it somewhere safe for future use.

Step 2: Log in to Gitlab's registry by running the following command:

$ docker login registry.gitlab.com

Enter your Gitlab username as the username and the Access Token generated in Step 1 as the password.

Step 3: Create a repository on Gitlab. For example, let's create a repository named "system".

Step 4: Build an image and make sure to name it the same as the Gitlab repository you created. For example:

$ docker build -t gitlab.com/hoaitx/system:latest .

Step 5: Push the image as usual:

$ docker push gitlab.com/hoaitx/system:latest

Step 6: To check if the image has been uploaded to the registry, go to the repository you created, then navigate to Deploy > Container Registry. You will see all the images along with their tags.

This registry can be used for pulling and pushing images just like any other registry. However, it is a private registry, so you need to log in to perform any operations.

Limits

One concern when using free services is the limitations that come with them. It's strange that there isn't any specific documentation regarding the storage limit for images in Gitlab's registry. A search in the community led to the conclusion that there are no storage limits! You can refer to the Gitlab forum for more information.

Premium

Me & the desire to "play with words"

Have you tried writing? And then failed or not satisfied? At 2coffee.dev we have had a hard time with writing. Don't be discouraged, because now we have a way to help you. Click to become a member now!

View all