ok, I went through an ad-hoc crash course in docker-compose....
I will write my findings in case someone else will encounter the same issues (centos 7, 'Quick-Start Installation and Tutorial' fail in section 'Test Zuul Pipelines'
#this will launch the zuul executor with '-d' for debug messages diff --git a/doc/source/examples/docker-compose.yaml b/doc/source/examples/docker-compose.yaml index 1123a577..bce08670 100644 --- a/doc/source/examples/docker-compose.yaml +++ b/doc/source/examples/docker-compose.yaml @@ -93,6 +93,7 @@ services: depends_on: - scheduler image: zuul/zuul-executor + command: "/usr/local/bin/zuul-executor -f -d" volumes: - "./etc_zuul/:/etc/zuul/:z" - "./playbooks/:/var/playbooks/:z"
#the output reveals that Ansible can't create user namespace executor_1 <snip> Ansible output: b"bwrap: No permissions to creating new namespace , likely because the kernel does not allow non-privileged user namespaces. On e.g. debian this can be enabled with 'sysctl kernel.unprivileged_userns_clone=1'."
#I'm using CentOS 7, not Debian mentioned in the comment above. In my case the kernel parameter has a different name. it should be > 0. It was already set to 15000
sudo sysctl user.max_user_namespaces
user.max_user_namespaces = 15000
#I had to update the kernel from 3.10 build 363 to 3.10 build 1160.36.2 to have user.max_user_namespaces take effect sudo yum update kernel sudo reboot
issue solved.
Thanks, Yaniv
On Wed, Aug 11, 2021 at 10:59 AM Yaniv Levy yaniv.levy@broadcom.com wrote:
Hi Jim,
Thank you for the answer.
(1) I'm having trouble finding out how to add '-d' and 'keep' to the docker-compose.yaml file can you post a diff?
(2) I executed a stand-alone ansible playbook on 'test/playbooks/testjob.yaml'. with 'host: all' it fails. with 'host: localhost' it passes. I guess that the yaml is valid.
ansible-playbook test1/playbooks/testjob.yaml [WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all'
PLAY [all] skipping: no hosts matched
PLAY RECAP
Thank you.
On Tue, Aug 10, 2021 at 10:50 PM James E. Blair jim@acmegating.com wrote:
Yaniv Levy yaniv.levy@broadcom.com writes:
Thank you Jim.
Is -'d' same as '–keep-jobdir' I found in the documentation here? https://zuul-ci.org/docs/zuul/discussion/components.html#executor
No, "-d" is debug which is separate from "--keep-jobdir".
how would I set '-d' or launch the zuul-executor with the option 'keep' within the context of the 'quick-start' docker-compose.yaml?
They are both global command line options for the process.
I have noticed that the directory ' ./etc_zuul/' contains zuul.conf and
is
mounted to the 'executor' container. Should I add something to
zuul.conf?
No, you would need to change the docker-compose.yaml file.
-Jim