Showing posts with label registry. Show all posts
Showing posts with label registry. Show all posts

Monday, July 24, 2017

Registry Option: SUSE Portus

An Open Source alternative to Docker Trusted Registry is Portus from SUSE. This is a front end to a private Open Source registry that allows for fine grained control of registry access and content: it can manage users, teams, and namespaces (no, not the kernel ones). It can integrate with LDAP for authentication and offers an audit trail, and can be extended for security scanning.
Portus dashboard with activity log
To play with Portus, we need:
  1. docker-compose.
  2. a private registry
  3. Portus

Thursday, July 21, 2016

Multi-Arch Registry and Images

It has been a while since multi-architecture support has been developed and brought upstream. Multi-architecture support allows to put several images behind a common identifier in a registry. With that, a consumer of the image won't have to think about pulling the right binary flavor of the image, it's done right automatically for him.

A couple of things play together for this magic:

Tuesday, July 19, 2016

A Private Registry. Building and Using

Recently, I received some questions on how to create a private registry. Specifically when going to a recent version, building on your own might make sense. Since describing this last (here and here), this can even be done simpler.

Let's start the build:

Sunday, January 31, 2016

"FROM golang" -- revisited

In this post, we created an image that deals with go-based containers. When tagging it golang, building works out of the box for most Dockerfiles.
Now that golang has been ported to s390x, we can look at this again, creating a golang image that bases on golang rather than gccgo:

Wednesday, January 6, 2016

Portus

As an extension to distribution/registry, SUSE has created an open source project called Portus. Portus comes offers a web UI and good control over users and teams dealing with images in a registry.

Wednesday, May 13, 2015

Public base images

https://registry.hub.docker.com/search?q=s390x shows base images available on Docker's public registry. Simply "docker pull <image>" to download them.
If you need to use a proxy, you can set the environment variable http_proxy (set it to http://proxy-address:port/) when starting the docker daemon.