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

Docker no such device error when running in non-interactive mode #2499

Closed
LesnyRumcajs opened this issue Feb 2, 2023 · 0 comments · Fixed by #2514
Closed

Docker no such device error when running in non-interactive mode #2499

LesnyRumcajs opened this issue Feb 2, 2023 · 0 comments · Fixed by #2514
Assignees
Labels

Comments

@LesnyRumcajs
Copy link
Member

Describe the bug

When running the container in non-interactive mode AND without the --encrypt-keystore false option we get an error like so:

❯ docker run  --init --rm ghcr.io/chainsafe/forest:latest  --chain calibnet
2023-02-02T09:44:35.910039Z  INFO forest: Using default calibnet config
2023-02-02T09:44:35.910741Z  INFO forest::daemon: Starting Forest daemon, version 0.4.1+git.a708b83
2023-02-02T09:44:35.910764Z  INFO forest_libp2p::service: Networking keystore not found!
2023-02-02T09:44:35.910935Z  INFO forest_utils::io: Permissions set to 0600 on File { fd: 8, path: "/home/forest/.local/share/forest/libp2p/keypair", read: false, write: true }
2023-02-02T09:44:35.911093Z  INFO forest::daemon: PeerId: 12D3KooWCJ3WDMsvajAuCB2cLzhHn2T9RdoNnJ9eSBE5hhwJriFK
Enter the keystore passphrase: Error: No such device or address (os error 6)

This does not occur when running the container in interactive mode OR when issuing the --encrypt-keystore false flag. It's probably a permission fiasco.

Expected behaviour

Forest should not fail.

Screenshots

Environment (please complete the following information):

  • OS: Fedora 37
  • Branch/commit 04130d5

Other information and links

@LesnyRumcajs LesnyRumcajs self-assigned this Feb 6, 2023
@LesnyRumcajs LesnyRumcajs added this to the Forest 🌲 Infrastructure milestone Feb 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant