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

Bitcoin Node running into errors #99

Open
debasish22 opened this issue Jun 6, 2022 · 6 comments
Open

Bitcoin Node running into errors #99

debasish22 opened this issue Jun 6, 2022 · 6 comments

Comments

@debasish22
Copy link

i am using this image through a compose file which used to work fine but now the node is not getting started , Attaching the error messages . Any help appreciated.

image

@RoccoMathijn
Copy link

Same here!

@uranik777
Copy link

uranik777 commented Aug 20, 2022

Same here! When will this be fixed?

2022-08-20T18:06:07Z

************************
EXCEPTION: St12system_error
Operation not permitted
bitcoin in AppInit()

2022-08-20T18:06:07Z Shutdown: In progress...
2022-08-20T18:06:07Z Shutdown: done

@nklyy
Copy link

nklyy commented Aug 29, 2022

Yea, same error
EXCEPTION: St12system_error Operation not permitted bitcoin in AppInit()

@saiaman
Copy link

saiaman commented Sep 1, 2022

solution : add --privileged to docker run

@mellertson
Copy link

mellertson commented Apr 2, 2023

solution : add --privileged to docker run

Seems like a potentiall risky thing to do, because using --priviledged will do the following, quoting from the docs:

The --privileged flag gives all capabilities to the container. When the operator executes docker run --privileged, Docker will enable access to all devices on the host as well as set some configuration in AppArmor or SELinux to allow the container nearly all the same access to the host as processes running outside containers on the host. Additional information about running with --privileged is available on the Docker Blog.

@a0ngo
Copy link

a0ngo commented Jan 7, 2025

Sorry for bumping an old thread, I ran into this issue with v28 with docker.
The solution was to upgrade docker engine version using the official docker instructions:
https://docs.docker.com/engine/install/ubuntu/#install-docker-engine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants