-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
The Docker container starts with an error #3115
Comments
Back to v2.14.0 ... everything works correctly |
Same problem here. Went back to v2.14.0 |
Same. I'm on a RPI. So Arm. |
We had an issue with the docker build so we rebuilt the v2.15.0 image. Can you try repulling it? |
I've tried this version: same problem.
I'm running this container on an ARM server on OCI using Ubuntu.
Em sex., 13 de dez. de 2024 às 14:03, Mike Cao ***@***.***>
escreveu:
… We had an issue with the docker build so we rebuilt the v2.15.0 image. Can
you try repulling it?
—
Reply to this email directly, view it on GitHub
<#3115 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC6W7AHUOS2BUKX32BBN34L2FMHOPAVCNFSM6AAAAABTR4VXHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBRHA3TIOBZGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Henrique Lobo Weissmann
Diretor Técnico
<https://www.facebook.com/itexto> <https://www.twitter.com/itexto>
<https://www.linkedin.com/company/itexto>
<https://www.instagram.com/itextobr>
*Tel:* +55 (31) 2573-1979 <+55(31)2573-1979>
*Email:* ***@***.***
*Web:* www.itexto.com.br
|
Now it works with v2.15.0 (amd64). |
I'm seeing this error when building v2.15.0 on amd64:
|
Same, just updated to v2.15.0:
Using |
|
After updating to 2.15 umami does not start. Went back to 2.14
|
Should be fixed in v2.15.1. |
Describe the Bug
The Docker container (Umami + PostgreSQL)starts with an error ...
Database
PostgreSQL
Relevant log output
Which Umami version are you using? (if relevant)
v2.15.0
Which browser are you using? (if relevant)
Safari, Chrome
How are you deploying your application? (if relevant)
No response
The text was updated successfully, but these errors were encountered: