-
Notifications
You must be signed in to change notification settings - Fork 41
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
permission denied issue in dev-net #459
Comments
Hi @pgwadapool, thanks for your feedback 🙂 Could send us the following information so that we can identify the issue?
|
I am following the steps outlined in the documentation I am running on Ubuntu 22.04 x86 Attached logs |
In 'docker-compose.yaml' generated file so that we avoid 'permission denied' erros as in #459
It looks like there are some permissions issues with your remote docker setup. In the mean time, we have added an option on the volumes of the |
This did not solve the problem. |
This was an issue in docker installation and this is now resolved at my end. Pls close the issue |
Hi @pgwadapool thanks for your feedback, I close the issue 👍 |
Context & versions
I am running dev-net as per the documentation using remote docker
Actual behavior
mithril-signer-node-pool1_1 | Error: InitializationError(Os { code: 13, kind: PermissionDenied, message: "Permission denied" })
mithril-signer-node-pool1_1 | {"msg":"Started","v":0,"name":"slog-rs","level":20,"time":"2022-08-27T04:24:38.210862051Z","hostname":"52c3ad6c4a16","pid":1,"config":"Config { cardano_cli_path: "/app/bin/cardano-cli", cardano_node_socket_path: "/data/ipc/node.sock", network_magic: Some(42), network: "devnet", aggregator_endpoint: "http://mithril-aggregator:8080/aggregator\", party_id: "pool1zpc8krqqdd7ahy20uqzqqj7hmskdelr3aplpncq8v3n9skmyq06", run_interval: 700, db_directory: "/data/db", data_stores_directory: "/data/mithril/signer-node-pool1/stores" }","run_mode":"dev"}
mithril-signer-node-pool1_1 | Error: InitializationError(Os { code: 13, kind: PermissionDenied, message: "Permission denied" })
I am not sure what the issue is
The text was updated successfully, but these errors were encountered: