-
Notifications
You must be signed in to change notification settings - Fork 508
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
/usr/bin/samba.sh: line 140: $2: unbound variable #219
Comments
Likely not related to your issue, but v2tec/watchtower has moved to containrrr/watchtower. The v2tec image hasn't been updated in a year :) |
Had no idea! I'll switch right away. |
@millermarkj line 140 is a function to setup a samba user... which your compose doesn't seem to be doing. Did updating the watchtower resolve the issue? |
No. I was able to resolve this by building my own container and updating the samba.sh script. There appears to be environment variable processing involved any env that STARTS with "USER". USERID meets that criteria. It seems you attempted to handle that case and clear the environment earlier, but for some reason that regex match doesn't end up unsetting the environment variable. Also, the loop that processes any env that starts with USER doesn't seem to handle the empty/missing case of USER= or USER="". |
Thanks for the bug report, I think that it should be fixed now. |
Have you pushed any changes? Git isn't showing any updates and the dperson/samba container pulled has the same hash. |
Doh! I've pushed the change now. I've been working on these while sitting in airports for a lot of travel that I've had to do just recently, jet lag doesn't help me remember details alas... |
I use v2tec/watchtower to keep my containers updated. samba updated last night and now won't run. Starting it manually reports:
Based on a prior issue I double-checked the syntax. But nothing seems to make it start. My docker-compose file:
The text was updated successfully, but these errors were encountered: