This repository has been archived by the owner on Jun 12, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you think should it be a bind mount instead of a volume?
--
I'm not sure I want to advocate people use their home directory over the named volume.
Given
homebox/Dockerfile
Line 47 in 673db41
the data should be persistent anyways
🤷
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you should mount the volume in a defined location for easy backups and access. home directory makes sense as there are the... user directories, configs and data. all backup solutions include the home directory by default.
if you really don't want to use the home directory as example, you can use
-v /path/to/data/folder:/data \
in the docker run, like linuxserver guys do it.