Dokploy / Dokploy/dokploy

Use external disk mount to store docker cache build and other related information

Open
#2,494 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

What problem will this feature address?

Hello, thanks for this project.

It would be nice to have the possibility to attach an external disk (volume) to a server (most providers allow this, e.g., Hetzner). This would make it possible to store the Docker build cache, logs, and other data on the external volume, so we wouldn’t consume resources from the main disk. As a result, applications would have more storage available to operate.

This also opens up the possibility of simplifying the implementation of #1670, since we would have a separate disk for backups. That disk could be detached from the main server, ensuring we don’t lose anything if the server is deleted.

Describe the solution you'd like

Panel in settings dashboard to select a disk to store specific information there - cache, logs, backups. Should have more than 1 selector if more than 1 disk is attached to a server and we may need to separate different metadata between different disks like - logs goes there, backups to another disk, etc.

Describe alternatives you've considered

We could probably just upgrade a server, but sometimes you don't need additional CPU\RAM for it and it will costs more in most cases.

Additional context

No response

Will you send a PR to implement it?

Maybe, need help

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the settings dashboard and the existing Docker cache, log, and backup storage paths. Review how attached server volumes are represented and determine how disk selection should work when multiple disks are available. Done means the scope and behavior for assigning each data category to an external disk are defined and implemented with appropriate validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, typescript
Domain
cloud, devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.