LDAP setup failing with multiple errors about gluu-docker

[alicederyn]

root@3e11a4c38965:/# ls -ld /etc/certs
dr-x------ 2 jetty jetty 1122 Jan 24 18:49 /etc/certs

[alicederyn]

This is being set in GLUU's setup.py:

            self.run([self.cmd_chown, '-R', 'jetty:jetty', self.certFolder])
            self.run([self.cmd_chmod, '-R', '500', self.certFolder])

I'm rather surprised nobody's hit this before, since this was committed 3 months ago?

[alicederyn]

I've fixed this in my local checkout by, instead of discarding the various folders generated by setup.py during docker build, copying them to an "images" directory, and then modifying gluu_endpoint to copy them back before running the LDAP server. Is this a bad approach in general?

Alternatively, if running setup.py locally, not on the image, is essential, I could create a new docker machine that maps the data directories elsewhere, runs setup.py and copies across the results (thus moving this step out of the docker build process), and have the LDAP machine wait for this to finish (signalling completion with a special file). Obviously as this is more complex I'd rather not bother—is there a security risk to leaving setup.py's results in the docker image?

[pi0]

@ChrisAlice Sorry reaching you out late. Actually this was the method i was previously using (creating an onpbuild image which runs and stores setup.py results inside image) But this method was very unstable as many components seems to have dependency on hostname (which we cannot change during build stage).

/bin/chmod: cannot access '/opt/node-v6.9.1-linux-x64/bin/': No such file or directory,

This is really not an issue, as we already include every dependency (see Dockerfile) and setup.py tries to do this again relying their customized and never released environment which they internally use to package gluu dep packages.

Gluu was under heavy changes during this project so things may be broken. I'll try to investigate breaking changes this weekend ;)

[oluies]

I didnt get it up and running also, is the README the current setup steps ?