Skip to content
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

docker compose up not work in v5.3.1, ushahidi-platform-1/ushahidi-platform_tasks-1 exited with code 1 #4517

Closed
kiang opened this issue Feb 3, 2023 · 2 comments

Comments

@kiang
Copy link

kiang commented Feb 3, 2023

Describe the bug
The two containers 'ushahidi-platform-1/ushahidi-platform_tasks-1can't run usingdocker compose up`

Where was the bug observed
Before the service running

To Reproduce
Steps to reproduce the behavior:

  1. Download v5.3.1 release and extract it
  2. Install the latest docker following https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository
  3. Execute command sudo docker compose up

Expected behavior
Run the container and can be access from browser.

Desktop Hardware Details (please complete the following information):

  • OS: Ubuntu 22.04.1 LTS
  • Docker version 23.0.0, build e92dd87
@kiang
Copy link
Author

kiang commented Feb 3, 2023

error messages:

ushahidi-mysql-1           | 2023-02-03T02:26:02.647858Z 3 [Note] Got an error reading communication packets
ushahidi-mysql-1           | 2023-02-03T02:26:02.648107Z 2 [Note] Got an error reading communication packets
ushahidi-platform_tasks-1  | truncate: cannot open 'storage/logs/lumen.log' for writing: No such file or directory
ushahidi-platform-1        | truncate: cannot open 'storage/logs/lumen.log' for writing: No such file or directory
ushahidi-platform-1 exited with code 1
ushahidi-platform_tasks-1 exited with code 1

@lupa18
Copy link

lupa18 commented Feb 16, 2023

I did the same and works. Why do you call docker-compose with sudo?

Main problems using this configuration comes with a wrong .env file.

Could you paste your .env file?

I also have problems there at storage but will publish another issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants