Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

came across CannotCreateConfigPath issue, but don't found any clues #9793

Closed
xiaods opened this issue Oct 22, 2018 · 4 comments
Closed

came across CannotCreateConfigPath issue, but don't found any clues #9793

xiaods opened this issue Oct 22, 2018 · 4 comments
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue.
Milestone

Comments

@xiaods
Copy link

xiaods commented Oct 22, 2018

Before filing a new issue, please provide the following information.

  • Parity Ethereum version: 2.1.3 docker
  • Operating system: linux
  • Installation: docker hub
  • Fully synchronized: yes
  • Network: ethereum
  • Restarted: yes

https://github.com/xiaods/ethereum-client-k8s-setup/blob/master/parity.yml

upgrade the yaml 's parity verison to v2.1.3, i always got errors:

Loading config file from /config/parity.toml
Error upgrading parity data: CannotCreateConfigPath


@ddorgan
Copy link
Collaborator

ddorgan commented Oct 22, 2018

@xiaods can you chown the data files and ensure they're owned by the user who's running the container and not the root user. Parity now runs as a non-root user in the container.

@xiaods
Copy link
Author

xiaods commented Oct 22, 2018

@ddorgan i can't found the parity-ethereum's dockerfile. i don't know the Dockerfile weather set a user, it is important for my setup. i use k8s deployment xml to declare the deployment, it will mount configMap and remote volume, i need to config it each other.

@jam10o-new
Copy link
Contributor

jam10o-new commented Oct 22, 2018 via email

@jam10o-new jam10o-new added the F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. label Oct 23, 2018
@xiaods
Copy link
Author

xiaods commented Oct 24, 2018

thanks, it resolve my case. thanks

@xiaods xiaods closed this as completed Oct 24, 2018
@5chdn 5chdn added this to the 2.2 milestone Oct 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue.
Projects
None yet
Development

No branches or pull requests

4 participants