I can't activate an existing module?

[Ae1080 (ahmed altayib)]

i have just installed the latest version of tryton from docker image as described in “How to run Tryton using Docke” from here How to run Tryton using Docker
the problem is that i can not activate any module for example account (version 7.0.2 as it is appear in details) although all dependencies modules are activated (currency,party,company,ir and res).
i am trying to activate the module from inside the erp from Adminstration/modules/modules then perform pending activation/upgrade after choosing the needed module to be activated then Start Upgrade the procces start and then an empty error message appear to command me to report the bug.

i run docker on virsualbox that run ubuntu 22.04.3 desktop

this is the first time to play with tryton … any help?

[udono]

Welcome @Ae1080, it’s good to have you here!

Do you have any error messages from the container where trytond is running in?

@Ae1080

although all dependencies modules are activated (currency,party,company,ir and res).

country is IMHO also depending.

did you try to install the account module via CLI, like:

trytond-admin --activate-dependencies -u account -d <DATABASE NAME>

[Ae1080 (ahmed altayib)]

@udono

Do you have any error messages from the container where trytond is running in?

no , just empty message from inside tryton web client.

@udono

country is IMHO also depending.

for account module not needed as it is not appear in dependencies tab. but i checked it and it is already activated with others(currency, party, ir , res , company , bank , user role, country) that is all activated modules, nothing else.

@udono

did you try to install the account module via CLI, like:

I am not familiar with docker but after i was played with it i can run it inside tryton container (tryton/tryton image) and the Traceback :

File “/usr/local/bin/trytond-admin”, line 31, in
admin.run(options)
File “/usr/local/lib/python3.11/dist-packages/trytond/admin.py”, line 31, in run
database.connect()
File “/usr/local/lib/python3.11/dist-packages/trytond/backend/sqlite/database.py”, line 365, in connect
self._make_uri(), uri=True,
^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/dist-packages/trytond/backend/sqlite/database.py”, line 439, in _make_uri
raise IOError(“Database ‘%s’ doesn’t exist!” % db_path)
OSError: Database ‘/var/lib/trytond/db/tryton.sqlite’ doesn’t exist!

[ced (Cédric Krier)]

@Ae1080

I am not familiar with docker but after i was played with it i can run it inside tryton container

You must launch the /entrypoint.sh in order to have the proper setup environment.

[Ae1080 (ahmed altayib)]

@ced

You must launch the /entrypoint.sh in order to have the proper setup environment.

this is my env

DB_PASSWORD=Zool1080
HOSTNAME=f39708c4bde7
DB_HOSTNAME=tryton-postgres
TRYTOND_CONFIG=/etc/trytond.conf
PWD=/
HOME=/var/lib/trytond
LANG=C.UTF-8
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=00:tw=30;42:ow=34;42:st=37;44:ex=01;32:.tar=01;31:.tgz=01;31:.arc=01;31:.arj=01;31:.taz=01;31:.lha=01;31:.lz4=01;31:.lzh=01;31:.lzma=01;31:.tlz=01;31:.txz=01;31:.tzo=01;31:.t7z=01;31:.zip=01;31:.z=01;31:.dz=01;31:.gz=01;31:.lrz=01;31:.lz=01;31:.lzo=01;31:.xz=01;31:.zst=01;31:.tzst=01;31:.bz2=01;31:.bz=01;31:.tbz=01;31:.tbz2=01;31:.tz=01;31:.deb=01;31:.rpm=01;31:.jar=01;31:.war=01;31:.ear=01;31:.sar=01;31:.rar=01;31:.alz=01;31:.ace=01;31:.zoo=01;31:.cpio=01;31:.7z=01;31:.rz=01;31:.cab=01;31:.wim=01;31:.swm=01;31:.dwm=01;31:.esd=01;31:.avif=01;35:.jpg=01;35:.jpeg=01;35:.mjpg=01;35:.mjpeg=01;35:.gif=01;35:.bmp=01;35:.pbm=01;35:.pgm=01;35:.ppm=01;35:.tga=01;35:.xbm=01;35:.xpm=01;35:.tif=01;35:.tiff=01;35:.png=01;35:.svg=01;35:.svgz=01;35:.mng=01;35:.pcx=01;35:.mov=01;35:.mpg=01;35:.mpeg=01;35:.m2v=01;35:.mkv=01;35:.webm=01;35:.webp=01;35:.ogm=01;35:.mp4=01;35:.m4v=01;35:.mp4v=01;35:.vob=01;35:.qt=01;35:.nuv=01;35:.wmv=01;35:.asf=01;35:.rm=01;35:.rmvb=01;35:.flc=01;35:.avi=01;35:.fli=01;35:.flv=01;35:.gl=01;35:.dl=01;35:.xcf=01;35:.xwd=01;35:.yuv=01;35:.cgm=01;35:.emf=01;35:.ogv=01;35:.ogx=01;35:.aac=00;36:.au=00;36:.flac=00;36:.m4a=00;36:.mid=00;36:.midi=00;36:.mka=00;36:.mp3=00;36:.mpc=00;36:.ogg=00;36:.ra=00;36:.wav=00;36:.oga=00;36:.opus=00;36:.spx=00;36:.xspf=00;36:~=00;90:#=00;90:.bak=00;90:.old=00;90:.orig=00;90:.part=00;90:.rej=00;90:.swp=00;90:.tmp=00;90:.dpkg-dist=00;90:.dpkg-old=00;90:.ucf-dist=00;90:.ucf-new=00;90:.ucf-old=00;90:.rpmnew=00;90:.rpmorig=00;90:.rpmsave=00;90:
TERM=xterm
SERIES=7.0
SHLVL=1
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
_=/usr/bin/env

the error still as the same.

[ced (Cédric Krier)]

Clearly you do not launch with the ENTRYPOINT /entrypoint.sh because you are missing the environment it is supposed to setup.
So you must run /entrypoint.sh bash before running any command when you enter the container with docker exec.
Or you must use docker run like described on Docker