rakeshtripathy
Hello,
I have upgraded Elixir version from 1.10 to 1.12.3 and erlang 22.2.6 to 23.3.4.18
I have set the global version after erlang installation.
asdf global erlang 23.3.4
.tool-version.ex
elixir 1.12.3-otp-23
erlang 23.3.4
In my dev environment I can see below :
Erlang/OTP 23 [erts-11.2.2.17] [source] [64-bit] [smp:2:2] [ds:2:2:10] [async-threads:1] [hipe]
Elixir 1.12.3 (compiled with Erlang/OTP 23)
But when I deploy it in test environment, I can see below
Erlang/OTP 24 [erts-12.3.2.9] [source] [64-bit] [smp:1:1] [ds:1:1:10] [async-threads:1] [jit]
warning: the VM is running with native name encoding of latin1 which may cause Elixir to malfunction as it expects utf8. Please ensure your locale is set to UTF-8 (which can be verified by running “locale” in your shell)
Interactive Elixir (1.12.3) - press Ctrl+C to exit (type h() ENTER for help)
Issue here is the OTP 24 is displaying in test environment and because of this few dependencies are not working. Please help to resolve this.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 8- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
aenglisc
How exactly is it deployed?
benwilson512
Tangentially you should aim to resolve this issue regardless of what Elixir / OTOP version you use.
al2o3cr
Related previous discussions:
rakeshtripathy
It is deployed via CI/CD pipeline, and as per the logic it should take the version from .tool-version.ex.
rakeshtripathy
yes, still I didn’t get the root cause and solution for this.
rakeshtripathy
As we are using cloak for data encryption/decryption, but it’s not supporting in OTP 24 and that gives issues to me.
aenglisc
Perhaps it should but apparently it is not. Would you mind sharing it?
al2o3cr
More details are the only thing that will help - saying “it is deployed with
azure_docker_build.yml” isn’t much to go on when something’s going wrong with the configuration in there.The system is doing what it’s configured to do; if it’s doing something that it “shouldn’t do”, or not doing something that it “should do” then the problem is with our understanding of the configuration that’s being supplied.