I have updated flyctl
. I was also working on getting things to work with --local-only
in the interim. The very first error I had when using --local-only
was that git wasn’t installed in the Docker container, and when mix tried to install a hex package via that package’s master branch on GitHub (instead of by a package version number), it wasn’t finding the git
executable. Since that’s the first error I encountered with --local-only
, I think there’s a decent chance it was the issue with the deploy as well.
That said, now after a few fixes I’m seeing this in the deploy output for both --local-only
and the regular deploy process:
Preparing to run: `/app/bin/my_app eval MyApp.Release.migrate` as nobody
2021/10/28 22:43:12 listening on [fdaa:0:3728:a7b:2295:9c64:b287:2]:22 (DNS: [fdaa::3]:53)
** (EXIT from #PID<0.94.0>) an exception was raised:
** (RuntimeError) SSL connection can not be established because `:ssl` application is not started,
you can add it to `extra_applications` in your `mix.exs`:
def application do
[extra_applications: [:ssl]]
end
(postgrex 0.15.10) lib/postgrex.ex:606: Postgrex.ensure_deps_started!/1
(postgrex 0.15.10) lib/postgrex.ex:548: Postgrex.child_spec/1
(ecto_sql 3.7.0) lib/ecto/adapters/sql.ex:609: Ecto.Adapters.SQL.init/3
(ecto 3.7.1) lib/ecto/repo/supervisor.ex:172: Ecto.Repo.Supervisor.init/1
(stdlib 3.15) supervisor.erl:330: :supervisor.init/1
(stdlib 3.15) gen_server.erl:423: :gen_server.init_it/2
(stdlib 3.15) gen_server.erl:390: :gen_server.init_it/6
(stdlib 3.15) proc_lib.erl:226: :proc_lib.init_p_do_apply/3
Main child exited normally with code: 1
Reaped child process with pid: 561 and signal: SIGUSR1, core dumped? false
Starting clean up.
Error Release command failed, deployment aborted
This fix does not seem to have any effect, and adding :ssl
to extra_applications
also does not seem to have any effect.