-
-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] USER_NAME cannot be set to an user that already exists in /etc/passwd #100
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
I can't replicate this, what's the actual username you're using?
|
"homeassistant", which doesn't seem relevant.
|
Oh, sorry, didn't notice the restart, yeah I need to fix that. I'll sort out a PR for it later today. |
Is there an existing issue for this?
Current Behavior
sshd won't start up after the first restart, due to the changes in #97
Expected Behavior
Start.
Steps To Reproduce
Have an empty/non-existent config folder, start it up once, and then restart it for the first time.
Environment
No response
CPU architecture
arm64
Docker creation
services: autossh: image: linuxserver/openssh-server:latest container_name: autossh restart: unless-stopped ports: - 22222:2222 - 8123:8123 environment: - PUID=1001 - PGID=1001 - TZ=Europe/Vienna - USER_NAME=randomusername # here's the culprit - PASSWORD_ACCESS=false - SUDO_ACCESS=false - PUBLIC_KEY_FILE=/authorized_keys volumes: - ./openssh_config:/config - ./authorized_keys:/authorized_keys:ro
Container logs
The text was updated successfully, but these errors were encountered: