Skip to content
This repository has been archived by the owner on Jun 12, 2024. It is now read-only.

Fix the docker run command in README.md #278

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,10 +16,13 @@
[Configuration & Docker Compose](https://hay-kot.github.io/homebox/quick-start)

```bash
docker run --name=homebox \
--restart=always \
--publish=3100:7745 \
ghcr.io/hay-kot/homebox:latest
docker run -d \
--name homebox \
--restart unless-stopped \
-p 3100:7745 \
-e TZ=Europe/Bucharest \
-v ${HOME}/.homebox:/data \
Copy link
Owner

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

VOLUME [ "/data" ]

the data should be persistent anyways

🤷

Copy link
Author

@rursache rursache Feb 16, 2023

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.

ghcr.io/hay-kot/homebox:latest
```

## Credits
Expand Down