build and publish docker image with persistent local data
- Dominant language
- Python
- Stars
- 26
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Currently there is already a `Dockerfile` [here](https://github.com/bitdust-io/devel/blob/master/Dockerfile) which is also published [here](https://hub.docker.com/r/bitdust/app1)
The issue is that data files used and generated by the app are stored only inside the container. So BitDust, running via docker image, does not have persistent storage.
It is also required to use ssh client to get into the running docker image, which is not what usually people do with apps running via Docker.
It would be great to have something like that to run BitDust app via docker:
`docker run -d -P --name bitdust_node_1 bitdust/bitdust -v $(pwd):/home/my-user-name/.bitdust`
Contributor guide
Research direction
Start with the existing Dockerfile linked in the issue and the example docker run command. Trace where the app stores and generates data inside the container, then check how the image is published at bitdust/app1. Done means a Docker-run BitDust instance keeps its data through container recreation and does not require SSH for normal use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100