Skip to content

fix: cycler not working correctly in docker without volume #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1k-off wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: cycler not working correctly in docker without volume #12

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
22 changes: 21 additions & 1 deletion pages/docker.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,13 +38,33 @@ models:
username: root
```

Run GoBackup in Docker.
### Run GoBackup in Docker.

```bash
docker run -d --name gobackup \
-v $(pwd)/gobackup:/etc/gobackup \
-v $(pwd)/cycler:/root/.gobackup/cycler \
-p 2703:2703 \
huacnlee/gobackup:latest
```

`/root/.gobackup/cycler` needs to be persisted for the cycler to work correctly. If this directory is not
persisted, the cycler will not be able to remove outdated backups after a container restart.

If you want to persist logs as well, instead of `/root/.gobackup/cycler`, you can use `/root/.gobackup` as a volume.

Now can access GoBackup Web UI at http://127.0.0.1:2703.

### Run GoBackup with docker compose.

```yaml
services:
gobackup:
image: huacnlee/gobackup:latest
ports:
- "127.0.0.1:2703:2703"
restart: unless-stopped
volumes:
- ./gobackup.yml:/etc/gobackup/gobackup.yml
- ./cycler:/root/.gobackup/cycler
```