Troubleshooting - When try start up the Odoo container

[christopherDallar]

What I found about how to solve problems when the Odoo container didn't up. For example, db service takes a lot of time to work

[christopherDallar]

Check that config/odoo.conf

The most error is not check the addons_path

addons_path = /mnt/extra-addons, /mnt/custom-addons, /mnt/another-addons

that have to math with volume of odoo container

volumes:
  - odoo-web-integra14:/var/lib/odoo
  - ./config:/etc/odoo
  - ./enterprise:/mnt/extra-addons
  - ./modules:/mnt/custom-addons
  - ./custom:/mnt/another-addons

[christopherDallar]

Out of container check Files Permissions

To change permissions : sudo chown $USER:$USER -R ./* -> sudo chown binaural12:binaural12 -R ./*

[christopherDallar]

When DB takes a lot of time to up

"I recommend using the restore script"

Download from this link: https://github.com/binaural-dev/script-backups/blob/master/restore_db.sh

How does it use?

1. Run de command

Command name:
restore_db

Arguments that allow:
[ -b DATABASE_CONTAINER ] [ -o ODOO_CONTAINER ] [-f FILE_ZIP] [-d DATABASE_NAME]

Note: The script Just supports files with .zip extensions

Example:

restore_db -b inpacol_db -o inpacol -f './binaural-dev-inpacol-staging-7393506_2023-03-06_193710_test_nofs.zip' -d db1

Run that script and then...

2. Fix the permissions of filestore folder into the odoo container odoo.

• Enter into the container:
  docker exec -it <odoo_container_name> bash -> docker exec -it pleni2 bash
• Go to: cd /var/lib/odoo/filestore
• Set permissions to odoo: chown odoo:odoo -R ./*

[christopherDallar]

Check if it is using the correct .env

Note: Check if the ports of PORT_SERVICE_HOST_ODOO, PG_ADMIN_HOST_PORT are not using by others containers

PROJECT_NAME=integr14bsmovil
PORT_SERVICE_HOST_ODOO=16000
PORT_SERVICE_CONTAINER_ODOO=8069
ODOO_RELEASE=latest
POSTGRES_IMG_VERSION=14
POSTGRES_DB=postgres
POSTGRES_PASSWORD=odoo
POSTGRES_USER=odoo
PG_ADMIN_HOST_PORT = 8010
PG_ADMIN_SERVICE_CONTAINER_PORT = 80

[christopherDallar]

Or just wait until the db service run (recommended
)