#hardfork-docker
1 messages · Page 1 of 1 (latest)
if you are on docker and planning for the migration,you are in big trouble , take a look into this issue and share your thoughts
https://github.com/anoma/namada-shielded-expedition/issues/360
is the problem just that there's no image for v0.31.10, or is it more complicated than that?
We use docker as well. Can we use release version 32.1 to do the migrations? that seems to build fine with the dockerfile in the namada repo
if i understand correctly, no because there is an intermediate step that needs 31.10, but the corresponding docker image is incorrect (it contains the 31.9 binaries)
we will try the v0.31.10,image and see if it works, but i guess the worse case scenario is that we can use the offical migration.json
using ``v0.31.10` docker image works
we have generated the migration.json file with the correct hash
but namada -V shows v0.31.9 , right ?
yeah