DevHeads.net

Postings by Mohammed Ahmed

New version of moodle container available on registry.centos.org

Hi,

Announcing availability of Moodle[1] container[2] for moodle version 3.5
now available on registry.centos.org.

[1] <a href="https://moodle.org/" title="https://moodle.org/">https://moodle.org/</a>
[2] <a href="https://registry.centos.org/centos/moodle" title="https://registry.centos.org/centos/moodle">https://registry.centos.org/centos/moodle</a>

sclo images on registry.centos.org namespace deprecated in favour of centos

Hi,

The Software Collections images on registry.centos.org were originally
available under the namespace 'sclo'.

For example : sclo/postgresql-96-centos7 is deprecated in favour of
centos/postgresql-95-centos7

Please make sure you update any usages of said images to reflect the new
name, as the old image names will be dropped from registry.centos.org soon.
I will send out another email, a couple of days before the said images are
dropped

Running openshift on arm64

Hi,

I was wondering if it was possible to deploy openshift on arm64. We need
this for building containers on the CentOS Container Pipeline.

I am aware that there was some talk around rpms for the same, and it would
be helpful if someone could point us to any resources.

Container image rebuilds (Sclorg)

Hi,

All images on the container pipeline are undergoing a rebuild based on
updated centos base images, which should finish in a few hours.

I will forward any failure messages to emails provided in Dockerfile
maintainer tags, if i can find them, and/or raise issues for the container
build failures.

In all other cases, it is highly recommended that you try out the newer
build of containers from Sclorg containers[1-18], to ensure the containers
maintain their functionality.

Container Pipeline image rebuild

Hi,

All images on the container pipeline are undergoing a rebuild based on
updated centos base images, which should finish in a few hours.

I will forward any failure messages to emails provided in Dockerfile
maintainer tags, if i can find them, and/or raise issues for the container
build failures.

In all other cases, it is highly recommended that you try out the newer
build of containers from CentOS Dockerfiles[1], to ensure the containers
maintain their functionality.

Updating notification emails for containers in pipeline.

Hi,

I was considering updating notification emails for the containers in the
container pipeline to maintainers for the respective containers.
(Currently, I single-handedly receive notifications for most of the
containers, which can be a bit overwhelming - hundreds of emails at-least
per day, in this case)

In line with this, the notification email for centos-dockerfiles kubernetes
containers have been updated to include Jason Brooks.

That of course, leaves the remaining containers, and it would be helpful if
i can know which would be the notification emails that you, the
maintainers, would l

Openshift Origin Containers for v1.2.1 and v1.3 on container pipeline.

Hi,

We currently have openshift origin containers being delivered through
the Container Pipeline.

However, with the release of openshift origin 1.3, we have to consider how
we are going to deliver containers for v1.2.1 and v1.3.

Currently, the dockerfiles basically do a yum install origin[1] and other
origin packages. This could possibly result in the latest origin rpms being
used even in 1.2.1 containers.

Update on status of CentOS Community Container Pipeline

Hi all,

Here is the update in for the work done recently, for the CentOS Community
Container Pipeline.

- There was an issue where the entry point of the container was running,
instead of the build / test / delivery scripts specified by the user. We
solved this by overriding entry point in all the stages.
- Setup a basic framework for running test suits, such as scans against
containers.

Update on status of CentOS Community Container Pipeline.

Hi all,

Here is the update for work recently done for the CentOS Community
Container Pipeline.

- Docker builds in the CCCP-Service were taking a long time for building
each images. We tracked down the issue and got in conclusion of building
the images sequentially. This increase the performance as the other option
of creating docker lvm pool is already in place.