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

Bug: docker-compose up -d fails during first install #841

Closed
1 of 2 tasks
naz opened this issue Jun 7, 2024 · 3 comments
Closed
1 of 2 tasks

Bug: docker-compose up -d fails during first install #841

naz opened this issue Jun 7, 2024 · 3 comments
Labels
🐛 Bug Something isn't working

Comments

@naz
Copy link

naz commented Jun 7, 2024

Where did this bug occur?

  • Local development
  • Self hosted app (i.e. Docker)

Describe the bug
When setting up Maybe on a self-hosted machine following setup instructions, the Run app with Docker Compose step fails with following error:

:~/docker/maybe$ docker-compose up -d
ERROR: The Compose file './docker-compose.yml' is invalid because:
services.app.environment.SELF_HOSTING_ENABLED contains true, which is an invalid type, it should be a string, number, or a null

To Reproduce
Steps to reproduce the behavior:

  1. ssh into the server
  2. follow the steps from self-hosting guide
  3. see the failure on the Run app with Docker Compose step

Expected behavior
The docker-compose up -d should create and run a fresh Maybe instance

Additional context
Might be an issue with the docker environment? My server is running on Docker version 20.10.12, build e91ed57

@naz naz added the 🐛 Bug Something isn't working label Jun 7, 2024
@MohamedEHJ
Copy link

I have the same problem
docker-compose version 1.29.2, build unknown
Docker version 26.0.2, build 3c863ff

@zachgoll
Copy link
Collaborator

zachgoll commented Jun 10, 2024

@naz can you try modifying your docker compose file like this and let me know if it fixes the problem?

environment:
  SELF_HOSTING_ENABLED: "true"
  DB_HOST: postgres
  RAILS_FORCE_SSL: "false"
  RAILS_ASSUME_SSL: "false"
  POSTGRES_USER: postgres
  GOOD_JOB_EXECUTION_MODE: async

@zachgoll
Copy link
Collaborator

I believe the solution I've outline above should work for everyone. Closing this out for now and can re-open if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants