Why did I agree to let people put the dogshit docker in my beautiful repo
I'm officially not gonna work on it after this fix, y'all are on your own with docker lol
Discussion
Remove it and tell them to fork off
I have a love/hate relationship with docker. I’m definitely comfortable and proficient with “containers,” but I’d rather not deal with it.
I have to change the Dockerfile and docker-compose.yml files to addapt them to my envirnment anyway, so it would be better if you removed them and left it fr the user to create their own.
It could be worse, imagine if it was flakes for nixos.
Is the error related with my PR or did something else change?
For some reason the first docker implementation nostr:nprofile1qqsrl7kr5my9n6423nwaktrsq2nwzzenal4e95p9k9826mu294jkv4cprdmhxue69uhksctkv4hzuemfwf5kumewdaexwtmrdpshgqgawaehxw309a5xzan9dchxw6tjd9hx7tn0wfnj7mm4w33x77qpremhxue69uhksctkv4hzuemfwf5kumewdaexwtmswf5hvct5v5n32399 made used a folder called haven which collides with my binary called haven, all just a mess, not your fault, I'm trying to clean it all up now
not me, not me... i'm innocent in this one :-D I haven't submitted pull requests to haven. (yet)
Just saw the changes to support Badger and the subsequent modifications to mounted volumes. While most of the containerisation work was done by someone else, feel free to remove the Docker and Docker Compose files from Haven on my end.
I'm happy to try and maintain Docker support in my repo, but I can't promise to keep it in sync with upstream in a timely manner (i.e., I'll likely only pull from upstream when I really want a new feature or bugfix).
Based off the screenshot, if you are trying to build the image locally, this could be a dns issue.
I never install stuff in my host machine, I always use .devcontainer