Error when running docker-compose run superdesk-server run python manage.py app:initialize_data

[sr33rajv]

Same issue on Ubuntu 20.x and 18.x
docker-compose run superdesk-server run python manage.py app:initialize_data
Starting root_mongodb_1 ... done
Starting root_elastic_1 ... done
Starting root_redis_1 ... done
waiting for elastic.done.
INFO:superdesk.backend_meta.backend_meta:version of 'superdesk-core': 2.5.dev0
INFO:superdesk.backend_meta.backend_meta:version of 'superdesk-planning': 2.6.0.dev0
Traceback (most recent call last):
File "/opt/venv/lib/python3.8/site-packages/reportlab/lib/utils.py", line 523, in open_for_read
return open_for_read_by_name(name,mode)
File "/opt/venv/lib/python3.8/site-packages/reportlab/lib/utils.py", line 463, in open_for_read_by_name
return open(name,mode)
FileNotFoundError: [Errno 2] No such file or directory: 'DejaVuSans.ttf'

During handling of the above exception, another exception occurred:

[petrjasek]

is this on broadcasting branch?

[sr33rajv]

No we used Master branch.

[petrjasek]

strange, there is no reportlab required there https://github.com/superdesk/superdesk/blob/master/server/requirements.txt

[petrjasek]

but if you add fonts-dejavu to https://github.com/superdesk/superdesk/blob/master/server/Dockerfile#L5-L13 it should work

[sr33rajv]

I tried to install superdesk on Multiple servers but same issue when intializing the data.

[bmg1919]

What other changes have you and/or your team made? I was unable to reproduce this error after adding reportlab to the server requirements. The superdesk core and planning module versions do not match output from the master branch either.

On the other hand, you can do as petrjasek said and install the font.

[sr33rajv]

What other changes have you and/or your team made? I was unable to reproduce this error after adding reportlab to the server requirements. The superdesk core and planning module versions do not match output from the master branch either.

We didn't change anything Just tried to install superdesk using this compose file https://github.com/superdesk/superdesk/blob/master/docker-compose.yml

[bmg1919]

I would start from scratch once more and watch the output.

Once you've cloned the repo into a new folder (git clone https://github.com/superdesk/superdesk.git), run git checkout. The output should be *master. If not, run git checkout master.

Then run sudo docker-compose up -d

That should make superdesk available at localhost:8080. Try logging in with admin/admin or running sudo docker-compose run superdesk-server python manage.py app:initialize_data.

[sr33rajv]

I would start from scratch once more and watch the output.

Once you've cloned the repo into a new folder (git clone https://github.com/superdesk/superdesk.git), run git checkout. The output should be *master. If not, run git checkout master.

Then run sudo docker-compose up -d

That should make superdesk available at localhost:8080. Try logging in with admin/admin or running sudo docker-compose run superdesk-server python manage.py app:initialize_data.

Tried this but same issue

[bmg1919]

That should not be possible working off the master branch. Unless it is a regional thing, not allowing you to obtain needed software during the install, but that does not explain why your containers are named differently or why it's obtaining different versions of superdesk-core or planning.

If you do have a newly acquired copy of superdesk, within the folder, try running sudo docker-compose build --no-cache. That should force it to rebuild the server and client regardless of how many times you've attempted to install. Then run sudo docker-compose up -d as usually to start it up and go from there.

[sr33rajv]

but if you add fonts-dejavu to https://github.com/superdesk/superdesk/blob/master/server/Dockerfile#L5-L13 it should work

The issue seems here when I add the fonts-dejavu in Dockerfile and run the initialize command it works fine.

[bmg1919]

Very true. That does not explain why you're not actually installing from the current master branch. That's where I got stuck on your issue..

[petrjasek]

seems like an issue with our github action which publishes images on every release, lately we were make some test releases from broadcasting branch where this reportlab is used, but that shouldn't be pushed to dockerhub.

[sr33rajv]

Ok so the dockerhub image issue should be resolved right?

[petrjasek]

yep it's updated now

[sr33rajv]

The new docker image is showing this error /opt/superdesk/docker/start.sh: line 26: exec: run: not found

[petrjasek]

that's when doing docker-compose up ?

[sr33rajv]

that's when doing docker-compose up ?

No the error is showing when i run docker-compose run superdesk-server run python manage.py app:initialize_data

[petrjasek]

imo there should be honcho run before python manage.py

[bmg1919]

Remove "run" from between superdesk-server and python. You're telling it to run "run" before python, which it can't find, causing it to error out before it has a chance to do anything else. There's most of the problem right there. Sorry it took so long to notice.

[unstence]

Remove "run" from between superdesk-server and python. You're telling it to run "run" before python, which it can't find, causing it to error out before it has a chance to do anything else. There's most of the problem right there. Sorry it took so long to notice.

This got me past that issue