SelfhostedPro / Yacht

A web interface for managing docker containers with an emphasis on templating to provide 1 click deployments. Think of it like a decentralized app store for servers that anyone can make packages for.
MIT License
3.32k stars 158 forks source link

[Bug Report] DISABLE_AUTH not working #575

Closed jrodriguesimg closed 4 weeks ago

jrodriguesimg commented 1 year ago

Describe the bug I passed DISABLE_AUTH to the container but it still asks for authentication

To Reproduce Steps to reproduce the behavior:

  1. create yacht container passing DISABLE_AUTH
    docker run -d --restart=always  -p 9000:8000 -v /var/run/docker.sock:/var/run/docker.sock -v yacht:/config --name yacht -e DISABLE_AUTH='true' -e SECRET_KEY='secrete' selfhostedpro/yacht
  2. open localhost:9000

Expected behavior It should not require authentication

Screenshots It requires authentication

Screenshot 2023-02-03 at 12 34 29

Desktop (please complete the following information):

Additional context I've never used yatch before. I'm looking for an alternative to portainer that does not require authentication to manage my local docker.

faulander commented 1 year ago

i came here for this exact feature which portainer will not implement. So sad to see it's not working :/

mkoertgen commented 1 year ago

DISABLE_AUTH=True is definitively working for me.

Here is a working example that I am using in a docker-compose.yml

...
  yacht:
    image: selfhostedpro/yacht:v0.0.7-alpha-2023-01-12--05
    ports: ["8000:8000"]
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
    environment: {"PUID":"0", "PGID":"0", "DISABLE_AUTH":"True"}
sutr90 commented 1 month ago

@mkoertgen Is the variable value Case sensitive? The OP has lowercase true, as opposed to Pascal case in your example.