Skip to content

Failing to start container after stop #32

Description

@jmmec

I've just started using this image a few days ago, but have already hit several instances where I've stopped / started the container, and it failed to start: the container silently exits with code 0 because the apachectl process immediately exits.

I believe the root cause of the apachectl process immediately exiting on "docker start" is because the container (somehow) didn't exit cleanly during the "docker stop" command. This log would get emitted during the failed "docker start" if you prevent the container from immediately exiting.

[Sat Jul 25 21:15:12.163295 2026] [core:warn] [pid 311] AH00098: pid file /var/run/apache2/apache2.pid overwritten -- Unclean shutdown of previous Apache run?

I believe this problem can be fixed by modifying the "/usr/sbin/run-lamp.sh" to always remove the "/var/run/apache2/apache2.pid" file before trying to start apachectl.

Thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions