Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-12858

Docker-nexus3 - When container dies (not gracefully) cache.lock remains in nexus-data volume. Should not be persistent.

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Docker-Nexus
    • Labels:

      Description

      I use an NFS-backed (azure-file) data volume for /nexus-data. When the container dies non-gracefully, the cache lock file often remains behind and has a NFS lock on it ("marked for deletion"), which prevents the container from restarting. As user tureba already pointed out in his comment on the sonatype/nexus3 repo on docker hub:

      Lock files, pid files, port files and (to some extent) temporary files are not supposed to be persisted! If the service dies suddenly and docker restarts it, we're in trouble if the pid files and lock files from the previous run are still in place because they will prevent the services from starting back up. So they must not be in /nexus-data.

      I'm pasting his comment here, since you can't link to it:

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jhesse Jeffry Hesse
            Last Updated By:
            Joe Tom Joe Tom
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Date of First Response:

                tigCommentSecurity.panel-title