Changing user ID in docker-compose to match system fails to start bitcoind
- Dominant language
- Dockerfile
- Stars
- 107
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
I do not want to use the user ID 1000 as this does not match my system. Instead I would like to use 996. The permissions of the data directory match this and I update the docker-compose.yml to use the correct user ID in the user field.
However this fails with the following error
`bitcoind | Error: filesystem error: cannot create directories: Permission denied [/.bitcoin/wallets]`
Is this something that I might be doing wrong? Or is this a bug? Or is it a feature request to allow user IDs other than 1000? I'm not sure but I would like to be able to do this
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with docker-compose.yml and reproduce the failure using a non-1000 user ID and a data directory owned by that ID. Trace how the container sets the user and Bitcoin data directory, then verify that bitcoind can create /.bitcoin/wallets with the configured ID. There are no tests or additional files mentioned in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100