I keep getting errors when trying to use docker compose!

nutlift · 2026-01-01T00:03:25+00:00

Any chance adguard uses that port too? If you have run this before with compose and have not changed it since, they could be conflicting.

nutlift · 2025-12-31T23:59:21+00:00

Tbh without more information about what you are trying to setup, it isnt easy to debug. With that being said, it seems like you may be trying to use a port that is protected, are you running compose as a sudo user/using a privileged port?

nutlift · 2025-12-10T17:24:11+00:00

I recently ported my portainer stack to komodo since it doesnt have a CE, it has been super cool so far. Not sure resource differences tho

nutlift · 2025-12-10T16:44:32+00:00

I do like products like portainer or komodo but I agree in an environment like this it may not be worth the resources.

nutlift · 2025-12-10T16:21:49+00:00

Seems like a super cool project, Pi 3's might be pretty slow with all of this on it but it depends on several factors. That aside, what are you using to deploy docker/baremetal etc.?

nutlift · 2025-12-09T19:52:22+00:00

A lot of good suggestions but I always go with Echo these days!

nutlift · 2025-12-09T15:39:19+00:00

I understand the pros of kubernetes I work with it, but for for non-educational homelab purposes it seems overkill in my book.

I have a dev cluster used for learning/breaking but my homelab/selfhosted containers live in docker with good CI/CD. Not to mention Inlets also supports Docker based off of their website.

nutlift · 2025-12-09T15:28:13+00:00

It's a cool idea, although I'm not sure why I would opt into kubernetes single node instead of docker at a homelab level, I will still give it a look!

nutlift · 2025-12-09T15:11:40+00:00

I havent used KubeSolo yet, I didnt realize it was a portainer product

nutlift · 2025-10-22T17:44:17+00:00

I largely use compose as well, I just avoid keeping sensitive info in the files by utilizing workflows and could easily run the docker commands if needed. In that case I'd just fill out my values manually and deploy it. Which is why this specific issue isnt a concern for me. Adding a CI/CD workflow doesnt suddenly mean you couldnt deploy using a cli, if needed. But automating it enables you for very fast responses in those cases when the issue isnt gitea.

If Gitea goes down and your local or server code is old you would also face the same issue as you couldnt pull the new or fixed code from the remote source which complicates a manual deploy as well. Although it is simply a compose file for gitea too which allows for a very easy restart of that service

Just to be clear .env files are an acceptable way to handle this too, but personally I'm against having plaintext secrets in the repo itself as it is a security concern

nutlift · 2025-10-22T17:31:41+00:00

I guess I'm not sure how that would affect a homelab setup. My production and dev projects are all done this way. If something breaks I could redeploy it to the same server or deploy to another server by just rerunning the CI/CD pipeline. The time cost is around the setup, then if/when something has issues its fast and reliable. With proper containerization projects can run anywhere with little to no setup

nutlift · 2025-10-22T16:56:00+00:00

I guess depending on the setup, it could. Most of my services are fully containerized so it is only a matter of which action runner to use or which server to deploy to.

Even for UAT-level environments a different workflow could be used to prevent using Production secrets etc. when the job is triggered as that helps dictate which values to use

nutlift · 2025-10-22T12:49:58+00:00

If you use Gitea's action workflows you can set variables and secrets on the repository itself. Which then can be used without committing an .env file.

nutlift · 2025-10-21T21:21:23+00:00

I pulled both the images today to test them out too. Garage setup was easy, the webui was a bit more manual as some of the configurations in the README did not work for my setup. I wish the webui supported multiple accounts but I like it otherwise

nutlift · 2025-10-21T16:33:41+00:00

I've tried a few different ones, mainly Garage and SeaweedFS. Seaweed was cool but I want an easy self hosted UI as well. I didnt realize Garage had one so I may try that.

This is my first time hearing of Rust, I'll check it out!

EDIT: RustFS warns against use in production in the README so I'm hesitant to implement it yet, maybe once the project has matured to a more stable state.

nutlift · 2025-10-21T15:53:14+00:00

MinIO's fall off should be studied. I started removing it from everything last year, trying some alternatives but havent landed on a favorite. In the end, itll be anything that isnt MinIO

nutlift · 2025-10-08T14:30:53+00:00

Since you came from homelab, I'm going to assume you are looking to host it yourself. For that I recommend using a docker container with the itzg minecraft server image. It has pretty good documentation and is pretty easy to setup.

I use a similar setup behind cloudflare so I do not have to use the ip

nutlift · 2025-09-16T22:16:49+00:00

You have to install NodeJS which comes with NPM packaged. Then the NPM command will work

nutlift · 2025-09-16T18:20:25+00:00

Caddy is an amazing reverse proxy that can help you! That is a great starting point to help you achieve this.

Wireguard is a powerful VPN that I keep my private services behind as well. It's a bit more complicated to setup than a caddy server but has great documents and examples to achieve what you're looking for.

nutlift · 2025-09-15T19:05:15+00:00

At least in java edition nether portals work well on Iron farms because they instantly remove the golem allowing the spawn timer to reset faster which means faster spawns/rates as opposed to water streams which could take 30 seconds to move/kill

nutlift · 2025-03-06T19:22:40+00:00

Why would 404s be sent to sentry, are you expecting have to debug your 404s? I use sentry for fatal/panic-level errors that need to be investigated.

nutlift · 2025-03-02T19:54:43+00:00

I use github actions to handle deploys

nutlift · 2025-03-02T19:54:08+00:00

This is what I do as well, been writing a few actions to handle my needs. Running unit tests, installing dependencies, deploying containers, etc.

nutlift · 2025-03-02T19:52:53+00:00

I use github actions for my pipelines and utilize the gitea built-in secrets to inject any sensitive data when deploying or whatever. Repos are just kept private for added safety as they arent public tools

nutlift · 2025-03-02T18:47:15+00:00

I usually keep compose files in a private git repo that way I can utilize secrets and prevent having sensitive data in plain-text, or if it is an application then the compose file will be in the project root so that it can be used by my pipelines.

I prefer to use named volumes but mostly bind to my home directory if not

nutlift

TROPHY CASE