Can't start Mobilizon 4 in Docker
Description
Mobilizon v4 Docker image doesn't start using the provided docker-compose file
Steps to Reproduce
- Get the docker-compose file and environment file from https://framagit.org/framasoft/joinmobilizon/docker
docker compose up -d
- Wait for all services to start
Expected behaviour:
Mobilizon should start and be available on port 4000
Actual behaviour:
The mobilizon container crashes with this error :
2023-12-06 09:12:08 ERROR! Config provider Config.Reader failed with:
2023-12-06 09:12:08 ** (FunctionClauseError) no function clause matching in System.get_env/2
2023-12-06 09:12:08 (elixir 1.15.7) lib/system.ex:664: System.get_env("MOBILIZON_SMTP_TLS", :if_available)
2023-12-06 09:12:08 /releases/4.0.0/runtime.exs:52: (file)
2023-12-06 09:12:08 (elixir 1.15.7) src/elixir.erl:396: :elixir.eval_external_handler/3
2023-12-06 09:12:08 (stdlib 5.1.1) erl_eval.erl:750: :erl_eval.do_apply/7
2023-12-06 09:12:08 (stdlib 5.1.1) erl_eval.erl:1026: :erl_eval.expr_list/7
2023-12-06 09:12:08 (stdlib 5.1.1) erl_eval.erl:292: :erl_eval.expr/6
2023-12-06 09:12:08 (stdlib 5.1.1) erl_eval.erl:282: :erl_eval.expr/6
2023-12-06 09:12:08 (stdlib 5.1.1) erl_eval.erl:283: :erl_eval.expr/6
2023-12-06 09:12:08
2023-12-06 09:12:08 Runtime terminating during boot ({function_clause,[{'Elixir.System',get_env,[<<"MOBILIZON_SMTP_TLS">>,if_available],[{file,"lib/system.ex"},{line,664}]},{elixir_eval,'__FILE__',1,[{file,"/releases/4.0.0/runtime.exs"},{line,52}]},{elixir,eval_external_handler,3,[{file,"src/elixir.erl"},{line,396}]},{erl_eval,do_apply,7,[{file,"erl_eval.erl"},{line,750}]},{erl_eval,expr_list,7,[{file,"erl_eval.erl"},{line,1026}]},{erl_eval,expr,6,[{file,"erl_eval.erl"},{line,292}]},{erl_eval,expr,6,[{file,"erl_eval.erl"},{line,282}]},{erl_eval,expr,6,[{file,"erl_eval.erl"},{line,283}]}]})
Reproduces how often:
All the times
Versions
Mobilizon v4 in Docker, using image from Docker hub framasoft/mobilizon:4.0.0
Additional Information
I tried to add the environment variable MOBILIZON_SMTP_TLS
to the container, but it doesn't solve the issue