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

Regression: Docker container does not start with v1.1.0 #360

Closed
1 task done
ledermann opened this issue Oct 14, 2020 · 8 comments
Closed
1 task done

Regression: Docker container does not start with v1.1.0 #360

ledermann opened this issue Oct 14, 2020 · 8 comments
Labels
bug Something isn't working

Comments

@ledermann
Copy link

ledermann commented Oct 14, 2020

Prerequisites

  • I have searched open and closed issues to make sure that the bug has not yet been reported.

Bug report

After updating the Docker image after v1.1.0 was released, the container cannot be started anymore. The logs are:

Loading plausible..
Starting dependencies..
Starting repos..
create Plausible.Repo database if it doesn't exist
create Plausible.ClickhouseRepo database if it doesn't exist
eation of Db successful!
/entrypoint.sh: line 11: exec: db: not found

Seems to be caused by #352. Ping @BobyMCbobs.

Sadly, a rollback is not simple because on Docker Hub there are no tags:
https://hub.docker.com/r/plausible/analytics/tags

To fix this issue for me, I checked-out the sources from v1.1.0, reverted 59acd4c, rebuild the image and pushed it to ledermann/plausible-fixed. This image works fine for me - I will delete it after there is a fixed official image.
Update: Just deleted my image, because the official image is fixed.

@ledermann ledermann added the bug Something isn't working label Oct 14, 2020
@ukutaht
Copy link
Contributor

ukutaht commented Oct 14, 2020

Reverting now, will release a patch update ASAP

@ukutaht
Copy link
Contributor

ukutaht commented Oct 14, 2020

Can you try the latest tag now

@ledermann
Copy link
Author

The image plausible/analytics:latest works fine now 👍

@bilyboy785
Copy link

Same issue here with latest tag

@BobyMCbobs
Copy link
Contributor

My apologies for the mishap. In local development I don't recall this issue.

This change leaves my issue (#352) unaddressed.
I will investigate further.

@BobyMCbobs
Copy link
Contributor

@ukutaht and @ledermann,

please try #362

@ukutaht
Copy link
Contributor

ukutaht commented Oct 16, 2020

@bilyboy785 Can you run the latest or v1.1.1 tag?

@ukutaht
Copy link
Contributor

ukutaht commented Oct 19, 2020

This should be fixed in v1.1.1. Closing

@ukutaht ukutaht closed this as completed Oct 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants