Yacht icon indicating copy to clipboard operation
Yacht copied to clipboard

[Bug Report] DISABLE_AUTH not working

Open jrodriguesimg opened this issue 2 years ago • 2 comments

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
  1. 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):

  • OS: docker for mac on M1 Max, Ventura 13.1
  • Browser: Brave
  • Yacht Version: lastest (IMAGE ID: d79060100eb7)

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.

jrodriguesimg avatar Feb 03 '23 12:02 jrodriguesimg

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

faulander avatar Feb 22 '23 19:02 faulander

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"}

mkoertgen avatar Feb 24 '23 19:02 mkoertgen

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

sutr90 avatar Jul 12 '24 19:07 sutr90