Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-28042

Fix Tomcat failing to start in Docker image due to missing ​/var/run/nuxeo/nuxeo.pid

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 11.1, 2021.0
    • Component/s: CI/CD

      Description

      After having fixed NXP-27988, see https://github.com/nuxeo/nuxeo/pull/3334, we've added a smoke test to run the image once it's built with the nuxeoctl start command and ensure that the exit code is 0, making the pipeline stage fail otherwise.

      This test is now failing with:

      22:34:25  Server started with process ID 118.
      22:34:25  Could not start process: /var/run/nuxeo/nuxeo.pid (No such file or directory)
      

       
      Possible lead: https://github.com/GoogleContainerTools/kaniko/issues/506
      Yet, when performing a docker describe on a running container, there seem to be no volumes in its Mounts.

      Maybe the problem is that

      • The 'maven' container of the pod used to build the image with Kaniko has
         /var/run/secrets/kubernetes.io/serviceaccount from jenkins-token-wrq8b (ro)
        

        in its Mounts

      • Kaniko magically performs the same mount on the built image.
      • Since it's readonly, the mkdir -p /var/run/nuxeo instruction in the Dockerfile fails silently...

      ------------------------------------------------------------------------------------------------------------------------------------------------
      In fact, most certainly a CentOS-related issue.
      Fixed by using another directory to store the pid: /var/pid/nuxeo.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 4 hours
                  4h