-t flag for the latest sebp/lighttpd container?

[Cheng-Ian-Liu]

Hi Seb,

May I know if the latest sebp/lighttpd requires a different docker run parameter to start successfully? I added the -t flag, but still have the following error. Thanks!

docker run --rm -t -v /root/cheng:/var/www/localhost/htdocs -p 8080:80 sebp/lighttpd

chmod: /dev/pts/0: No such file or directory
2021-11-09 05:13:07: configfile.c.1290) opening errorlog '/dev/pts/0' failed: Permission denied
2021-11-09 05:13:07: server.c.1509) Opening errorlog failed. Going down.

[spujadas]

Hi Ian, nothing’s changed in the image other than bumping up the version of lighttpd.

You were right to add the -t flag (#8 #10), but it’s strange that it doesn’t solve the issue.

Can’t reproduce on my end unfortunately, as adding -t prevents the error.

Without the flag:

~/lighttpd-docker$ docker run --rm -v $(pwd)/www:/var/www/localhost/htdocs -p 8001:80 sebp/lighttpd
chmod: /dev/pts/0: No such file or directory
2021-11-10 17:14:55: configfile.c.1290) opening errorlog '/dev/pts/0' failed: Permission denied
2021-11-10 17:14:55: server.c.1509) Opening errorlog failed. Going down.

With the flag:

~/lighttpd-docker$ docker run --rm -t -v $(pwd)/www:/var/www/localhost/htdocs -p 8001:80 sebp/lighttpd
2021-11-10 17:14:59: server.c.1513) server started (lighttpd/1.4.59)

Not that it should make much of difference, but here’s my version of Docker:

$ docker --version
Docker version 20.10.8, build 3967b7d

Fired up a fresh VM, and observed the exact same behaviour as above.

You could try to forcefully delete all your existing lighttpd images and containers running off these images, in pure "have you tried turning it off and on again" fashion, but other than that, as I can’t reproduce the issue I don’t see how to help with this one.

Is anyone else having this issue?