-
Notifications
You must be signed in to change notification settings - Fork 52
Error upgrading parity data: CannotCreateConfigPath #76
Comments
this solves it for me
|
@drandreaskrueger can you please re-try with the latest master. See: #77 |
@drandreaskrueger yes older versions of the docker image ran as root rather than the parity user. The PR merged fixes some permission issues due to this change. |
yes - but perhaps not before November. Actually, are you in Berlin? Then we should meet in person! |
Yes I will be at the web3 summit, it would be great to speak to you in person. |
Thanks. I think I had done Will try again, but probably only after devcon?
yesyesyes. |
Can I close this one? |
I'm still seeing this issue running |
David, we also saw this last Thursday. You had a very quick fix for it though. |
Is there some sort of a quick-fix for this? |
@ilhanu sure, basically do a chown -R on the data dir to the user you're running docker as. In parity-deploy if you create a new data dir (e.g. after a clean.sh) it will now mkdir the data dirs before starting the container the first time. This works around the permissions issue inside the container. |
Closing issue. |
? Couldn't you simply make this part of ./clean.sh somehow ? |
Happy New Year :-) |
Reappeared. See here #87 (comment) Please try to invent a solution which does not need machine specific user interaction, otherwise it is hard to include parity-deploy.sh in other tools. Thanks. |
Just tried that, but ... nope:
ends with
|
only when I do this, it works:
but that means accepting that it fails once, and I do not know if it causes other problems later. |
@ddorgan ? |
Can you please the branch in here: #94 |
you merged that to master now, right? |
Tried it out, just now:
yes it works. Well done. So I do not need to manually create
anymore? |
and the following includes patches for v1.11.11:
and ... it also works. Cool, thanks a lot. Well done. |
Now @ddorgan this issue can be closed lol. |
instantsealWhy not store the above, and these blocks here for future testing purposes, when you improve this great tool: aura
|
results in
The text was updated successfully, but these errors were encountered: