containers-a8 / docker-base-image-one-step Goto Github PK

Checking the status and extracting the PID using the following command worked locally of

pid=$(ps x | grep "${TOMCAT_PATH}" | grep -v grep |cut -d ' ' -f 1)
However it returned blanks when executed in a container.

Switched the checking to use pgrep. Tried both the variants

pid= $(pgrep -f tomcat/bin/bootstrap)
pid= $(/usr/bin/pgrep -f tomcat/bin/bootstrap)

Both resulted in command not found

To check the behaviour, i logged into the container and executed the commands and made the following observation(s):

1. cut returned blanks
2. pgrep worked well and returned the expected values.

Using the RHEL image requires active subscription.

Error messages that were encountered

1. (when using the file as-is) - https://artifactorypilot.srv.******.com:50990/artifactory/wdp-001_yum/docker-base/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: artifactorypilot.srv.*****.com; Name or service not known"
   Trying other mirror.
2. Upon removing references to artifactory - Loaded plugins: ovl, product-id, search-disabled-repos, subscription-manager
   This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.

Error getting repository data for rhel-server-rpms, repository not found

3. There are no enabled repos.
    Run "yum repolist all" to see the repos you have.
    To enable Red Hat Subscription Management repositories:
        subscription-manager repos --enable
    To enable custom repositories:
        yum-config-manager --enable

During the creation of a stage (in the delivery pipeline) or updating an existing stage, the error message - "There was a problem saving this stage" appears and the stage is not saved

Everytime the pipeline gets executed this message shows up

2016-11-24 23:09:35 UTC : LOGMET setup failed with return code 2
Need to figure out what's happening here?

The behaviour of monitoring and logging is inconsistent (i.e the logs only show up sometimes). We haven't identified a pattern as to when it works and when it doesn't.

The wrapper script - catalina_wrapper.sh invokes the register function on a container startup. However if the container is restarted this function is not invoked

The deregister function is not invoked in the following scenarios:

1. Stop the container.
2. Restart the container.

When the service image is built on top of the base image, the container fails on start up with the error message:

Manglu-mbp/Downloads:$cf ic logs 806f3ed9-d73
'open /root/Procfile: permission denied
'open /root/Procfile: permission denied