{"id":"garage","name":"Garage","version":"1.1.0","description":"An open-source distributed object storage service tailored for self-hosting.","logo":"garage-logo.svg","links":{"github":"https://github.com/deuxfleurs-org/garage","website":"https://garagehq.deuxfleurs.fr/","docs":"https://garagehq.deuxfleurs.fr/documentation/quick-start/"},"tags":["storage"]}
Template Description
Creates a garage instance that can be used as an S3 location.
Originally created by @jonykalavera on GitHub (Jun 12, 2025).
### Template Name
Garage
### Template URL
https://github.com/jonykalavera/dokploy-templates/blob/main/blueprints/garage/template.toml
### Docker Compose Link
https://github.com/jonykalavera/dokploy-templates/blob/main/blueprints/garage/docker-compose.yml
### Resources
```json
{
"id": "garage",
"name": "Garage",
"version": "1.1.0",
"description": "An open-source distributed object storage service tailored for self-hosting.",
"logo": "garage-logo.svg",
"links": {
"github": "https://github.com/deuxfleurs-org/garage",
"website": "https://garagehq.deuxfleurs.fr/",
"docs": "https://garagehq.deuxfleurs.fr/documentation/quick-start/"
},
"tags": [
"storage"
]
}
```
### Template Description
Creates a garage instance that can be used as an S3 location.
### Will you send a PR to implement it?
Yes https://github.com/Dokploy/templates/pull/180
I wanted to ask if this template working correctly or is there any configuration needed after template install. I already tried using the template as is, but is seems I'am unable to create a bucket/api is broken
@manh21 commented on GitHub (Sep 7, 2025):
I wanted to ask if this template working correctly or is there any configuration needed after template install. I already tried using the template as is, but is seems I'am unable to create a bucket/api is broken
<img width="1220" height="600" alt="Image" src="https://github.com/user-attachments/assets/497f12e3-a067-4e38-b338-ce82670b1b1b" />
@manh21
I just tried it again with a completely fresh instance and it worked without issues.
I noticed that in my logs all requests go to /v1 while yours go to /v2.
That might be the issue but tbh I am not sure why your calls even go to /v2 in the first place.
Here are my logs for comparison:
@vniehues commented on GitHub (Sep 13, 2025):
@manh21
I just tried it again with a completely fresh instance and it worked without issues.
I noticed that in my logs all requests go to `/v1` while yours go to `/v2`.
That might be the issue but tbh I am not sure why your calls even go to `/v2` in the first place.
Here are my logs for comparison:
<img width="1493" height="1024" alt="Image" src="https://github.com/user-attachments/assets/7058d7bc-9473-47d2-acaf-a1e61adf291b" />
That being said v1 is being deprecated and my logs show the correct behavior to hit v2 enpoint, with latest garage webgui.
In the template file I notice that garage is prefixes with version 1.1 and web gui prefixes with latest. I think that's the issues
@manh21 commented on GitHub (Sep 14, 2025):
I think your container image probably being cached not using latest web gui as per template.
Also garage has major version bump to v2. https://garagehq.deuxfleurs.fr/blog/2025-06-garage-v2/
That being said v1 is being deprecated and my logs show the correct behavior to hit v2 enpoint, with latest garage webgui.
In the template file I notice that garage is prefixes with version 1.1 and web gui prefixes with latest. I think that's the issues
Yes I just tried it! It is a combination of garage being used with the older version and the web-ui being used with latest.
It worked for me because of the cache but it does fail on fresh installs.
I'll update the template today - for now you can manually overwrite the versions in the docker compose before deploying.
Thank you for your help in figuring this out!
@vniehues commented on GitHub (Sep 14, 2025):
Yes I just tried it! It is a combination of garage being used with the older version and the web-ui being used with latest.
It worked for me because of the cache but it does fail on fresh installs.
I'll update the template today - for now you can manually overwrite the versions in the docker compose before deploying.
Thank you for your help in figuring this out!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @jonykalavera on GitHub (Jun 12, 2025).
Template Name
Garage
Template URL
https://github.com/jonykalavera/dokploy-templates/blob/main/blueprints/garage/template.toml
Docker Compose Link
https://github.com/jonykalavera/dokploy-templates/blob/main/blueprints/garage/docker-compose.yml
Resources
Template Description
Creates a garage instance that can be used as an S3 location.
Will you send a PR to implement it?
Yes https://github.com/Dokploy/templates/pull/180
@vniehues commented on GitHub (Aug 23, 2025):
@jonykalavera fyi: I added this with #297 and fixed storage separation with #298 (pending)
@manh21 commented on GitHub (Sep 7, 2025):
I wanted to ask if this template working correctly or is there any configuration needed after template install. I already tried using the template as is, but is seems I'am unable to create a bucket/api is broken
@vniehues commented on GitHub (Sep 7, 2025):
I have deployed it multiple times now and I did not face this error.
Can you take a look at the logs?
@manh21 commented on GitHub (Sep 7, 2025):
@vniehues commented on GitHub (Sep 13, 2025):
@manh21
I just tried it again with a completely fresh instance and it worked without issues.
I noticed that in my logs all requests go to
/v1while yours go to/v2.That might be the issue but tbh I am not sure why your calls even go to
/v2in the first place.Here are my logs for comparison:
@manh21 commented on GitHub (Sep 14, 2025):
I think your container image probably being cached not using latest web gui as per template.
Also garage has major version bump to v2. https://garagehq.deuxfleurs.fr/blog/2025-06-garage-v2/
That being said v1 is being deprecated and my logs show the correct behavior to hit v2 enpoint, with latest garage webgui.
In the template file I notice that garage is prefixes with version 1.1 and web gui prefixes with latest. I think that's the issues
@vniehues commented on GitHub (Sep 14, 2025):
Yes I just tried it! It is a combination of garage being used with the older version and the web-ui being used with latest.
It worked for me because of the cache but it does fail on fresh installs.
I'll update the template today - for now you can manually overwrite the versions in the docker compose before deploying.
Thank you for your help in figuring this out!
@vniehues commented on GitHub (Sep 14, 2025):
This should be fixed once https://github.com/Dokploy/templates/pull/367 is merged.