After CA API Developer Portal upgrade 4.5 to 5.1 Containers are not starting permission denied unknown

Products

• CA API Developer Portal

Issue/Introduction

After upgrade using YUM (as this is an offline install) from portal 4.5 to 5.1 the containers are failing to start. 

./portal.sh start

shows,

Updating service portal_db-upgrade-rbac (id: someid)
image caapim/db-upgrade-rbac:5.1.2 could not be accessed on a registry to record
its digest. Each node will access caapim/db-upgrade-rbac:5.1.2 independently,
possibly leading to different nodes running different
versions of the image.

Checking to see if DB schema update is needed....................................................................................

Portal logs contained errors,

dockerd[22665]: time="Date/timestamp" level=error msg="fatal task error" error="starting container failed: OCI runtime create failed: container_linux.go:380: starting container process caused: setup user: permission denied: unknown" module=node/agent/taskmanager

 

Resolution

This can happen with the default enforcement mode. 

You can set selinux to permissive

# setenforce 0

 

This will allow the containers to start.