-
Notifications
You must be signed in to change notification settings - Fork 102
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
Error on RPi4: Cannot start openeats web, api and nginx #143
Comments
Hi, In your
to:
For the database I'm using:
Here the link to my repositories: Have a nice day |
Hi Starto96,
You have any ideas, what went wrong? |
A small addition, when the container openeats_web_1 is running, I cannot enter the web-page. The error: 403 Forbidden |
Crap, I wish I remembered the details, but I had the same issue a while back... apologies for not being more directly helpful. But as I recall, the transient behavior of the docker web container is normal--the fact that you're able to load the page confirms that. The part that's broken seems to be the API's ability to display data from the database in the web ui. Perhaps attach to the database container and check logs for permissions related issues? Or now that I think about it, maybe I solved the issue by spinning up my own Mariadb container and forcing OpenEats to use that? |
Here is an extrace of the log of the container openeats_api_1 (maybe that helps): (mysql.W002) MariaDB Strict Mode is not set for database connection 'default' Operations to perform: Apply all migrations: admin, auth, authtoken, contenttypes, ingredient, list, menu, news, rating, recipe, recipe_groups, sessions, sites Running migrations: No migrations to apply. Your models have changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. 0 static files copied to '/code/static-files', 170 unmodified. |
Hi, i can confirm what saucedge said. The openeats_web_1 just builds the website and then put it in the volume of the openeats_nginx_1 container. I think i also had one time the same problem. Can you please show me what did you put in your en_prod.list file? |
Have a look in the attachement. Thanks for your response. |
mmm... i know that you should not do this but try to set: |
No, it's not working. I deleted all the containers and set it up agauin from scratch, but no change. What happened is, that the openeats-DB is not created automatically, shouldn't it? |
I'm not sure if with mariadb is possible to create automatically the database. I've create by hand because i already had one running for also other applications. The thing that there is no content at the beginning is normal, I think there is a way to put example recipes. Should be written somewhere in the documentation. What does happen if you click on the Alle Rezepte durchsuchen? Does it load something or there is just a spinning wheel? |
When I click there a loadihg circle appears and never stops. Here the log of the api-container: Apply all migrations: admin, auth, authtoken, contenttypes, ingredient, list, menu, news, rating, recipe, recipe_groups, sessions, sites Running migrations: No migrations to apply. Your models have changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. 0 static files copied to '/code/static-files', 170 unmodified. Starting OpenEats as root [2021-03-04 13:32:20 +0000] [10] [INFO] Starting gunicorn 20.0.4 [2021-03-04 13:32:20 +0000] [10] [INFO] Listening at: http://0.0.0.0:8000 (10) [2021-03-04 13:32:20 +0000] [10] [INFO] Using worker: sync [2021-03-04 13:32:20 +0000] [12] [INFO] Booting worker with pid: 12 [2021-03-04 13:32:20 +0000] [13] [INFO] Booting worker with pid: 13 [2021-03-04 13:32:20 +0000] [14] [INFO] Booting worker with pid: 14 [2021-03-04 13:32:20 +0000] [15] [INFO] Booting worker with pid: 15 [2021-03-04 13:32:20 +0000] [16] [INFO] Booting worker with pid: 16 |
this: "Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them." changes nothing |
Ok this means is actually all working beside the communication between the website and the api. Can you try to delete the NODE_API_URL=http://localhost from the env_prod.list? |
Sure, you mean just remove the blue highlighted part? And then restart the api and nginx container? |
you can delete also the variable and then restart all the container |
Sorry, but no changes |
mmm then i really don't know. You are using the docker-prod.yml file right? |
I'm sorry it didn't work. I just post here my settings of the env_prod.list and of my docker-prod.yml. I hope it can help you env_prod.list
docker-prod.yml
The ****** is just because i didn't want to publish username, password and key ;) |
I know this issue is old, but i wanted to post my config that works on armv7 (Pi4). I combined the prod docker-compose files into one. This is much easier in my opinion.
As for my env file, i use:
I use an external reverse proxy to point my domain (https://food.domain.com) to Then i spin up the containers using Whenever the images are pulled and created i run:
The mariadb container does not have the correct database, so i enter the container, logs in, creates the database and confirms the database has been created. Then i exit mysql and finally exit the container. Next i want to setup the database schema:
And finally i start the containers again. This step might not be needed, but i wanted to recompile the static files to make sure:
I checked this setup on two different hosts and confirmed that it works. I hope this helps people that have issues with running openeats on arm. |
The error in the logs:
standard_init_linux.go:219: exec user process caused: exec format error
I am using the default configuration for docker and I am running it on a RPi 4 with the new 64 bits rpi os (debian based)
The text was updated successfully, but these errors were encountered: