#53 build container image on quay.io
Closed 2 years ago by dcavalca. Opened 2 years ago by dcavalca.

This is pending on https://bugzilla.redhat.com/show_bug.cgi?id=1960699 getting sorted out first


Created https://quay.io/organization/centoshyperscale and the related team, comment with your quay.io account here to get added. Also created https://pagure.io/centos-sig-hyperscale/containers-releng with an initial script to build a base container without using the upstream one, as that bug is still unresolved.

Also filed https://pagure.io/centos-infra/issue/331 to get a SIG members email alias as I had to use my personal email to setup the quay account.

Uh, clearly I messed something up:

$ podman run -dt quay.io/repository/centoshyperscale/centos /bin/bash
Trying to pull quay.io/repository/centoshyperscale/centos:latest...
  Requesting bear token: invalid status code from registry 400 (Bad Request)
Error: Error initializing source docker://quay.io/repository/centoshyperscale/centos:latest: Requesting bear token: invalid status code from registry 400 (Bad Request)

Ah, I had the wrong url, this seems to be working:

[dcavalca@tardis containers-releng]$ podman run -dt quay.io/centoshyperscale/centos /bin/bash
Trying to pull quay.io/centoshyperscale/centos:latest...
Getting image source signatures
Copying blob abd651f17f80 done  
Copying config 97135069ae done  
Writing manifest to image destination
Storing signatures
56a69f7f130c4bba9cdb50e5c799c5089082f60ef4b483a4d2e735c6216bfd7f
[dcavalca@tardis containers-releng]$ podman attach 56a69f7f130c4bba9cdb50e5c799c5089082f60ef4b483a4d2e735c6216bfd7f
bash-4.4# systemctl --version
systemd 248 (v248.2-1.2.hs.el8)
+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified
bash-4.4# 

This was done a while ago. Filed https://pagure.io/centos-sig-hyperscale/sig/issue/91 to track the CI automation work.

Metadata Update from @dcavalca:
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata