search

wardenenv / warden

Warden is a CLI utility for orchestrating Docker based developer environments
https://warden.dev
MIT License
418 stars 168 forks source link

How to run without docker desktop for Linux #723

Closed ortoDev closed 1 year ago

ortoDev commented 1 year ago

Version of Warden

0.14.1

Operating System and Installation Method

Debian12 via brew

Describe the Bug

Docker Desktop for linux has severe permissions problems that makes warden unusable. There is a way to run warden without having docker desktop installed?

To Reproduce

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected Behavior

No response

Additional context

No response

bap14 commented 1 year ago

Warden requires a docker services. It doesn't have to be Docker Desktop, you can replace it with something like OrbStack for MacOS, Lima or Colima, containerd with nerdctl. Now you may have to add some aliases if the solution doesn't automatically have an alias for the "docker" command.

That being said, I'd like to hear what permissions problems you're having with Docker Desktop and Warden.

ortoDev commented 1 year ago

@bap14 Docker desktop changes project folder's ownership. It sets as 100999:100999 I'have tryed to add my user to that group ID but I can't still have write permission on the folder.

Can't I run warden with docker engine only? (I'm on Debian12 with Cinnamon)

bap14 commented 1 year ago

@ortoDev Warden requires a Docker engine that is compatible with the standard Docker commands (docker ps, docker compose, docker network, etc.). Docker Desktop is just the simplest solution for non-linux environments.

ortoDev commented 1 year ago

Thanks @bap14 Now I have a running warden svc on my machine only with docker engine. But when I try to reach http://mailhog.warden.test/ it gives me "Server not found". I've already mapped *test to 127.0.0.1 on my hosts file.

I need to add manually every host in my hosts file to see them in browser

bap14 commented 1 year ago

@ortoDev So if you go to https://traefik.warden.test do you see the Traefik dashboard? If not, then I'd ask you to run dig traefik.warden.test to ensure that returns as 127.0.0.1. If not, then you have an issue with your resolver setup that you'd need to investigate further.