OdooLS crashes in devcontainer when indexing items
Your setup Version: 1.0.4 Operating System: Ubuntu IDE and/or Integration tool (for example: Vscode - official extension): vscode
Describe the bug We are installing Odoo LS in our devcontainer using this profile
[[config]]
name = "Odoo by Adhoc"
odoo_path = "/home/odoo/src/odoo"
addons_paths = ["/home/odoo/custom/repositories/sale","/home/odoo/src/enterprise","/home/odoo/src/odoo/addons","/home/odoo/src/odoo/odoo/addons"]
and the server keeps crashing when is indexing the items. This are the logs:
[Info - 2:43:02 PM] Starting the extension.
Error waiting for process 6405: ECHILD: No child processes
Building new Odoo knowledge database
[Info - 2:43:11 PM] Detected sys.path: ["", "/usr/local/lib/python312.zip", "/usr/local/lib/python3.12", "/usr/local/lib/python3.12/lib-dynload", "/home/odoo/venv/lib/python3.12/site-packages", "__editable__.odoo-19.0.finder.__path_hook__"]
[Info - 2:43:11 PM] Adding sys.path: /usr/local/lib/python3.12
[Info - 2:43:11 PM] Adding sys.path: /usr/local/lib/python3.12/lib-dynload
[Info - 2:43:11 PM] Adding sys.path: /home/odoo/venv/lib/python3.12/site-packages
[Info - 2:43:11 PM] Detected sys.version_info: [3, 12, 12, "final", 0]
[Info - 2:43:13 PM] Building Database
[Info - 2:43:13 PM] Odoo version: 19.0.0
[Error - 2:43:16 PM] Failed to read file /home/odoo/src/enterprise/l10n_cl_edi_factoring/template/aec_template.xml, with error No such file or directory (os error 2)
[Error - 2:43:18 PM] Failed to read file /home/odoo/venv/lib/python3.12/site-packages/xlwt/BIFFRecords.py, with error stream did not contain valid UTF-8
[Error - 2:43:22 PM] Failed to read file /home/odoo/venv/lib/python3.12/site-packages/xlwt/UnicodeUtils.py, with error stream did not contain valid UTF-8
[Info - 2:44:15 PM] Connection to server got closed. Server will restart.
true
Building new Odoo knowledge database
Error waiting for process 6405: ECHILD: No child processes
[Info - 2:44:15 PM] Detected sys.path: ["", "/usr/local/lib/python312.zip", "/usr/local/lib/python3.12", "/usr/local/lib/python3.12/lib-dynload", "/home/odoo/venv/lib/python3.12/site-packages", "__editable__.odoo-19.0.finder.__path_hook__"]
[Info - 2:44:15 PM] Adding sys.path: /usr/local/lib/python3.12
[Info - 2:44:15 PM] Adding sys.path: /usr/local/lib/python3.12/lib-dynload
[Info - 2:44:15 PM] Adding sys.path: /home/odoo/venv/lib/python3.12/site-packages
[Info - 2:44:15 PM] Detected sys.version_info: [3, 12, 12, "final", 0]
[Info - 2:44:16 PM] Building Database
[Info - 2:44:16 PM] Odoo version: 19.0.0
[Error - 2:44:20 PM] Failed to read file /home/odoo/src/enterprise/l10n_cl_edi_factoring/template/aec_template.xml, with error No such file or directory (os error 2)
[Error - 2:44:25 PM] Failed to read file /home/odoo/venv/lib/python3.12/site-packages/xlwt/BIFFRecords.py, with error stream did not contain valid UTF-8
[Error - 2:44:53 PM] Failed to read file /home/odoo/venv/lib/python3.12/site-packages/xlwt/UnicodeUtils.py, with error stream did not contain valid UTF-8
[Info - 2:45:37 PM] Connection to server got closed. Server will restart.
true
Building new Odoo knowledge database
Error waiting for process 6405: ECHILD: No child processes
[Info - 2:45:38 PM] Detected sys.path: ["", "/usr/local/lib/python312.zip", "/usr/local/lib/python3.12", "/usr/local/lib/python3.12/lib-dynload", "/home/odoo/venv/lib/python3.12/site-packages", "__editable__.odoo-19.0.finder.__path_hook__"]
[Info - 2:45:38 PM] Adding sys.path: /usr/local/lib/python3.12
[Info - 2:45:38 PM] Adding sys.path: /usr/local/lib/python3.12/lib-dynload
[Info - 2:45:38 PM] Adding sys.path: /home/odoo/venv/lib/python3.12/site-packages
[Info - 2:45:38 PM] Detected sys.version_info: [3, 12, 12, "final", 0]
[Info - 2:45:38 PM] Building Database
[Info - 2:45:38 PM] Odoo version: 19.0.0
[Error - 2:45:43 PM] Failed to read file /home/odoo/src/enterprise/l10n_cl_edi_factoring/template/aec_template.xml, with error No such file or directory (os error 2)
[Error - 2:45:51 PM] Failed to read file /home/odoo/venv/lib/python3.12/site-packages/xlwt/BIFFRecords.py, with error stream did not contain valid UTF-8
[Error - 2:45:51 PM] Failed to read file /home/odoo/venv/lib/python3.12/site-packages/xlwt/UnicodeUtils.py, with error stream did not contain valid UTF-8
We also tried with 1.1.0 version.
This is our folder structure:
in custom/repositories we have our addons.
@joa-adhoc Hello Joaquin Arroyo!
Thank you for reporting it, seems like an issue with containerized envorinments, which we have not thoroughly tested yet.
We will work on it and update the issue when we have a fix for it
Thank you again
@joa-adhoc
Hello!
I am trying to reproduce the issue on a devcontainer.
I managed to get it working with a minimal setup on my side, I think I need more information from you to know why you are facing issues.
- What docker image are you using, or at least what base image it is based on ?
- Could you share the server logs with me, that would help me a lot in identifying the issue, you can find the log at
~/.vscode-server/extensions/odoo.odoo-1.0.4-linux-x64/logsinside the dev container.
Looking forward to hearing
@mmahrouss Hi! We’re using a devcontainer with a private image based on:
FROM python:3.12-slim-bookworm
Odoo runs inside a virtualenv created as a non-privileged user:
su $ODOO_USER -c "python -m venv $ODOO_HOME/venv"
Here are the logs from inside the devcontainer:
odoo_logs.2025-11-28-18.2222.log
Let me know if you need me to test anything else. Thanks!
@lef-adhoc Hello.
Okay it seems that the issue is not from the devcontainer per se.
- The errors from
Failed to read filedo not crash the language server, and it just skips those files, and that is okay. - "Error waiting for process 6405: ECHILD: No child processes" Is due to the server process dying due to an unrecoverable error.
- Looking at the logs you provided it does seem like we have an internal server error, likely caused by some sort of a cyclic import. We are currently debugging it, to try and catch it instead of having a server crash.
I hope that clears things a bit for you. Will update the issue when the bug is resolved!
Thank you for following up
@mmahrouss Thanks for the clarification! I’ll stay tuned and test the fix as soon as it’s available.