Improve Docker registry listing tool
a project by rbranco
Updated over 2 years ago. 1 hackers ♥️. 1 follower.

Project Description

regview is a heavily modified fork of the (no longer maintained) reg tool by Jess Frazelle for listing images in a Docker registry. Some features of reg were removed (like the webserver, to make it only cli) and others added. Some bugs were fixed (and PR's submitted) and others added as well.

Goal for this Hackweek

I plan to add some features like the --format option to customize output and maybe add some more unit tests.

It would be nice to also find an ideal way to tweak the number of goroutines. Care must be taken as, during initial development, I was warned that I was DDOS'ing our registry. This appears to be no longer the case. But one can do an initial scan and record all requests & replies to setup a server to service only those requests.

registry.suse.com implements pagination. SOLVED:

Resources

https://github.com/ricardobranco777/regview

Join this project

Looking for hackers with the skills:

golang registry docker containers

This project is part of:

Hack Week 22

Activity

  • over 2 years ago: paulgonin liked this project.
  • over 2 years ago: rbranco added keyword "containers" to this project.
  • over 2 years ago: rbranco removed keyword podman from this project.
  • over 2 years ago: rbranco started this project.
  • over 2 years ago: rbranco added keyword "registry" to this project.
  • over 2 years ago: rbranco added keyword "docker" to this project.
  • over 2 years ago: rbranco added keyword "podman" to this project.
  • over 2 years ago: rbranco added keyword "golang" to this project.
  • over 2 years ago: rbranco originated this project.


    • Comments

    • rbranco
      over 2 years ago by rbranco | Reply

      The pagination issue was solved by passing ?n=1000 to /v2/_catalog since, by default, Docker Distribution returns only 100 entries.

    Similar Projects

    terraform-provider-feilong by e_bischoff

    Project Description

    People need to test operating systems and applications on s390 platform.

    Installation from scratch solutions include:

    • just deploy and provision manually add-emoji (with the help of ftpboot script, if you are at SUSE)
    • use s3270 terminal emulation (used by openQA people?)
    • use LXC from IBM to start CP commands and analyze the results
    • use zPXE to do some PXE-alike booting (used by the orthos team?)
    • use tessia to install from scratch using autoyast
    • use libvirt for s390 to do some nested virtualization on some already deployed z/VM system
    • directly install a Linux kernel on a LPAR and use kvm + libvirt from there

    Deployment from image solutions include:

    • use ICIC web interface (openstack in disguise, contributed by IBM)
    • use ICIC from the openstack terraform provider (used by Rancher QA)
    • use zvm_ansible to control SMAPI
    • connect directly to SMAPI low-level socket interface

    IBM Cloud Infrastructure Center (ICIC) harnesses the Feilong API, but you can use Feilong without installing ICIC, provided you set up a "z/VM cloud connector" into one of your VMs following this schema.

    What about writing a terraform Feilong provider, just like we have the terraform libvirt provider? That would allow to transparently call Feilong from your main.tf files to deploy and destroy resources on your system/z.

    Other Feilong-based solutions include:

    • make libvirt Feilong-aware
    • simply call Feilong from shell scripts with curl
    • use zvmconnector client python library from Feilong
    • use zthin part of Feilong to directly command SMAPI.

    Goal for Hackweek 23

    My final goal is to be able to easily deploy and provision VMs automatically on a z/VM system, in a way that people might enjoy even outside of SUSE.

    My technical preference is to write a terraform provider plugin, as it is the approach that involves the least software components for our deployments, while remaining clean, and compatible with our existing development infrastructure.

    Goals for Hackweek 24

    Feilong provider works and is used internally by SUSE Manager team. Let's push it forward!

    Let's add support for fiberchannel disks and multipath.

    Possible goals for Hackweek 25

    Modernization, maturity, and maintenance.