Persistence of TOR Address Upon Destruction of Container
Open
- Dominant language
- Go
- Stars
- 617
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
How can I reuse the data that is created in the data directory when recreating a container from a mounted volume?
The current behaviour seems to create a brand new entry in the `data` directory and also a different TOR address when I load a new container with the /data folder mounted from the host.
Contributor guide
Research direction
Start by reproducing the container recreation described in the issue with /data mounted from the host, then inspect how the data directory and mounted volume are initialized. Done means recreating the container reuses the existing data and preserves the same TOR address.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100