Skip to content
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

/app/functions.sh: line 69: self_cid: unbound variable #542

Closed
ghost opened this issue May 17, 2019 · 8 comments
Closed

/app/functions.sh: line 69: self_cid: unbound variable #542

ghost opened this issue May 17, 2019 · 8 comments
Labels
kind/bug Issue reporting a bug

Comments

@ghost
Copy link

ghost commented May 17, 2019

I can't seem to be able to start the container anymore. I get the following in the log when I try:

/app/functions.sh: line 69: self_cid: unbound variable
Error: can't get nginx-proxy container ID !
Check that you are doing one of the following :
        - Use the --volumes-from option to mount volumes from the nginx-proxy container.
        - Set the NGINX_PROXY_CONTAINER env var on the letsencrypt-companion container to the name of the nginx-proxy container.
        - Label the nginx-proxy container to use with 'com.github.jrcs.letsencrypt_nginx_proxy_companion.nginx_proxy'.

My docker commandline is as follows:

docker run -d --name nginx-proxy-letsencrypt --volumes-from nginx-proxy -v /var/run/docker.sock:/var/run/docker.sock:ro jrcs/letsencrypt-nginx-proxy-companion

I've been trying tonnes of permutations of this over the last few hours and now I'm ready to give up. Does anyone have an idea what might be going on? Let me know if you require any additional info.

@buchdag
Copy link
Member

buchdag commented May 17, 2019

What version of the container are you using ?

@ghost
Copy link
Author

ghost commented May 17, 2019

:latest (sorry, forgot to note that I just updated my entire stack)

@buchdag
Copy link
Member

buchdag commented May 17, 2019

What version where you using prior to the update ?

Could you try with v1.11 and v1.10 ?

@ghost
Copy link
Author

ghost commented May 17, 2019

Ah! v1.10 seems to work!

@buchdag buchdag added the kind/bug Issue reporting a bug label May 17, 2019
@buchdag
Copy link
Member

buchdag commented May 17, 2019

I think I identified the issue, can you try with duch/letsencrypt-nginx-proxy-companion:542 ?

@ghost
Copy link
Author

ghost commented May 17, 2019

That looks like it works, yes.

@buchdag
Copy link
Member

buchdag commented May 17, 2019

Fix committed to master / latest

Released v1.11.1 with the fix and pushed it to Dockerhub as both v1.11 and v1.11.1.

Thanks for reporting the issue.

@buchdag
Copy link
Member

buchdag commented May 17, 2019

Try to stick to tagged release whenever possible, using latest tends to make issue identification harder.

bingozb pushed a commit to bingozb/docker-letsencrypt-nginx-proxy-companion that referenced this issue Dec 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issue reporting a bug
Projects
None yet
Development

No branches or pull requests

1 participant