Closed ghost closed 5 years ago
We faced the same issue and had to fix the dependency to distillery to a version prior to 2.1.x:
{:distillery, "~> 2.0.0"}
Thanks for the report. It looks like distillery 2.1.0 changed the names of these mix tasks (presumably to avoid clashing with new Elixir 1.9 tasks). I'll see what I can do, but in the meantime, yes, I recommend pinning to ~> 2.0.0
.
I just pushed a new release of the runtime. It adjusts what task it calls based on what version of distillery is present in your mix.lock
(and it also supports calling the Elixir 1.9 release task if distillery is not present at all).
Thanks for this. I'm not using this runtime but had a (Mix) The task "release" could not be found
when building my Docker image and I didn't notice that Distillery changed its mix tasks names.
When trying to deploy a distillery release, the deployment fails as step 12 with no mix release task found.