Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

alpine-apache doesn't start, could not create PID file #71

Open
gyger opened this issue Jan 8, 2017 · 1 comment
Open

alpine-apache doesn't start, could not create PID file #71

gyger opened this issue Jan 8, 2017 · 1 comment

Comments

@gyger
Copy link

gyger commented Jan 8, 2017

I use the base package alpine-apache to additionally install
php-apache2.

  RUN apk add --update \
          php-apache2 \
          php-sqlite3 \
          php-xml \
          php-curl \
          php-dom \
          php-iconv \
          php-pdo_sqlite \
          php-json \
          php-ctype \
        && rm -rf /var/cache/apk/*

When I try to start the container I get the following errors

Jän 08 22:56:15 <hostname> docker[19307]: [Sun Jan 08 21:56:15.136430 2017] [core:error] [pid 201] (2)No such file or directory: AH00099: could not create /run/apache2/http
Jän 08 22:56:15 <hostname> docker[19307]: [Sun Jan 08 21:56:15.136455 2017] [core:error] [pid 201] AH00100: httpd: could not log pid to file /run/apache2/httpd.pid

Any ideas where this could come from? In the beginning my containers were working, this only happened after I rebuild it in the recent weeks (i think around two weeks ago).

@kungfoome
Copy link

kungfoome commented Aug 29, 2017

This is still an issue. 2.0.1. it seems like /run/apache2 is not created. When I try to create the directory in my Dockerfile, it says it already exists. When I run the container, i look and it doesn't exist. Not sure whats going on here

This is running directly from the registry, creating a Dockerfile, nothing works.

@smebberson any ideas?

It seems like something removes these directories on init. Maybe s6? had to create directory inside the run script instead. see pr #89 and #88

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants