When running the official kubo container, if you have configuration scripts in /container-init.d executing ipfs config and similar, the container will fall on its face if a migration is needed. The output then is:
Note that running migrations is a task automatically performed by the ipfs when.... so you would normally not need to run the fs-repo-migrations tool.
Even though this is word by word correct it doesn't address the fact that a containerized setup most probably will have some sort of "declarative" configuration happening in /container-init.d/ scripts before the ipfs daemon command is run. So in this case you actually have to force the manual update before doing config, making it less of an edge case as it is being made out to be.
When running the official kubo container, if you have configuration scripts in
/container-init.dexecutingipfs configand similar, the container will fall on its face if a migration is needed. The output then is:Going to
run.mdyou find the mention:Even though this is word by word correct it doesn't address the fact that a containerized setup most probably will have some sort of "declarative" configuration happening in
/container-init.d/scripts before theipfs daemoncommand is run. So in this case you actually have to force the manual update before doing config, making it less of an edge case as it is being made out to be.Can we address this somehow in the documentation?