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

Ensure that container can be restarted #310

Merged
merged 1 commit into from
Sep 13, 2018
Merged

Ensure that container can be restarted #310

merged 1 commit into from
Sep 13, 2018

Conversation

guenhter
Copy link
Contributor

When the file /tmp/.X99-lock is available on startup of Xvfb, the process does not start.
So the script basically deletes this on startup.
Usually, this file should be cleaned by the Xfvb process itself, that's why the --retry is specified. This waits for the process to exit for the defined period of time.

@petrsloup petrsloup merged commit 0c42fdd into maptiler:master Sep 13, 2018
@petrsloup
Copy link
Member

Yes, this might help. Thanks!

@guenhter
Copy link
Contributor Author

Great to see this merged.
When can we expect a new Docker-Tag in the docker registry (except the latest)?

@guenhter guenhter deleted the fix-restart branch September 14, 2018 05:57
@petrsloup
Copy link
Member

I just created a v2.4.0 release which contains this change.

@KleggerKoder
Copy link

I encountered this problem yesterday using the command line npm install on Debian 9.
Had to use following command before calling tileserver-gl to get it working
Xvfb :1 -screen 0 1024x768x24 </dev/null & export DISPLAY=":1"

Is this fixed now on NPM?

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

Successfully merging this pull request may close these issues.

3 participants