-
Notifications
You must be signed in to change notification settings - Fork 7.8k
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
Migrations failing on latest Docker image #3826
Comments
Thanks for sharing. You seem to have an invalid workflow obj in your db. Would you be able to look into the db and tell us if the nodes object is |
I just checked my DB and the The migration table contains these migrations: '1', '1588157391238', 'InitialMigration1588157391238' |
I also have the same error with the latest Docker image 0.189.0 and MariaDB database. Downgrading to 0.188.0 solved the issue. |
@couquino what version of MySQL are you running? Cannot reproduce with version 8. @alexandervnuchkov What version of MariaDB are you running? |
$ mariadb --version
mariadb Ver 15.1 Distrib 10.9.1-MariaDB, for debian-linux-gnu (aarch64) using EditLine wrapper |
@mutdmour (lscr.io/linuxserver/mariadb) |
Also receiving the same error over here with the latest update and MariaDB: My |
thanks was able to reproduce it and address the issue |
hi guys, kubectl logs -n n8n n8n-9bd96d9bc-vz8xm --follow TypeError: nodes.forEach is not a function Database version: "mariadb:10.8" |
Got fixed with PR #3832 and released with |
Describe the bug
Just after the latest update of the Docker image (n8nio/n8n:latest@sha256:3b9eb2c6996bbae3044033a4bc4c18108b6de218562ded2ae3f36f9d9aa66980), the container is unhealthy and I now have these errors in logs
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The migration should execute fine
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: