Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

run.md unclear communication for container users. #187

Open
kiriakos opened this issue Jan 4, 2024 · 0 comments
Open

run.md unclear communication for container users. #187

kiriakos opened this issue Jan 4, 2024 · 0 comments
Labels
help wanted Seeking public contribution on this issue kind/bug A bug in existing code (including security flaws) P2 Medium: Good to have, but can wait until someone steps up topic/docs Documentation

Comments

@kiriakos
Copy link

kiriakos commented Jan 4, 2024

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:

Error: ipfs repo needs migration, please run migration tool.
See https://github.com/ipfs/fs-repo-migrations/blob/master/run.md
Sorry for the inconvenience. In the future, these will run automatically.

Going to run.md you find the mention:

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.

Can we address this somehow in the documentation?

@kiriakos kiriakos added the need/triage Needs initial labeling and prioritization label Jan 4, 2024
@lidel lidel added kind/bug A bug in existing code (including security flaws) help wanted Seeking public contribution on this issue P2 Medium: Good to have, but can wait until someone steps up topic/docs Documentation and removed need/triage Needs initial labeling and prioritization labels Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Seeking public contribution on this issue kind/bug A bug in existing code (including security flaws) P2 Medium: Good to have, but can wait until someone steps up topic/docs Documentation
Projects
None yet
Development

No branches or pull requests

2 participants