# LDAP string in Docker env

**URL:** <https://forum.ansible.com/t/ldap-string-in-docker-env/16833>\
**Category:** Ansible Project\
**Created:** [November 20, 2014, 2:56pm UTC](https://forum.ansible.com/t/ldap-string-in-docker-env/16833 "2014-11-20T14:56:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vincent\_Van\_der\_Kuss](https://avatars.discourse-cdn.com/v4/letter/v/7c8e57/32.png) [@Vincent\_Van\_der\_Kuss](https://forum.ansible.com/u/Vincent_Van_der_Kuss)\
**Post date:** [November 20, 2014, 2:56pm UTC](https://forum.ansible.com/t/ldap-string-in-docker-env/16833/1 "2014-11-20T14:56:42Z")

</div>

Hi,

I'm deploying a docker container where I pass an env variable in the  
docker module. The problem is that the parser cuts of a part of the  
value because it contains '=' signs.

this is the part from the playbook :

env="LDAP\_BIND\_DN="cn=user,dc=domain,dc=local"

when I look at the env var in the configuration file after the  
container has started i see following value :

cn=user

I assume the parser cuts everything off after first comma following a '=' sign.

Is there any way to escape this?

Vincent

---

<div class="post-metadata">

**Author:** ![Tomasz\_Kontusz](https://avatars.discourse-cdn.com/v4/letter/t/bc79bd/32.png) [@Tomasz\_Kontusz](https://forum.ansible.com/u/Tomasz_Kontusz)\
**Post date:** [November 20, 2014, 4:12pm UTC](https://forum.ansible.com/t/ldap-string-in-docker-env/16833/2 "2014-11-20T16:12:06Z")

</div>

You can use complex args, or try to escape the quotation mark that’s part of the value with \

Vincent Van der Kussen [vincent.vanderkussen@gmail.com](mailto:vincent.vanderkussen@gmail.com) napisał:

---

<div class="post-metadata">

**Author:** ![Vincent\_Van\_der\_Kuss](https://avatars.discourse-cdn.com/v4/letter/v/7c8e57/32.png) [@Vincent\_Van\_der\_Kuss](https://forum.ansible.com/u/Vincent_Van_der_Kuss)\
**Post date:** [November 23, 2014, 11:03am UTC](https://forum.ansible.com/t/ldap-string-in-docker-env/16833/3 "2014-11-23T11:03:31Z")

</div>

Complex args indeed fixed the issue.  
thx.