Ansible is pretty clear about it: the target system has a read only filesystem. Fix that and things will work.
On Fri, 10 Nov 2017 at 14:47, ManiGandan T <[email protected]> wrote: > Container.yml : > version: '2' > settings: > conductor_base: alpine:3.4 > services: > ansible.node-container: > from: "node:alpine" > roles: > - node_container > ports: > - '3001:3001' > user: node > > Command Used : > sudo ansible-container --debug build > > Main.yml > > Main.yml > > - name: Install dumb init > get_url: > url: > > https://github.com/Yelp/dumb-init/releases/download/v1.2.0/dumb-init_1.2.0_amd64 > dest: /usr/bin/dumb-init > owner: root > group: root > mode: 0775 > environment: > http_proxy: "http://xxx-proxy-out.xxx.com:8080"; > https_proxy: "http://xxx-proxy-out.xxxx.com:8080"; > HTTP_PROXY: "http://xxx-proxy-out.xxxx.com:8080"; > HTTPS_PROXY: "http://xx-proxy-out.xxx.com:8080"; > > Logs: > changed = module.set_fs_attributes_if_different(file_args, False) > File > "/tmp/ansible_3VUnyg/ansible_modlib.zip/ansible/module_utils/basic.py", > line 1450, in set_fs_attributes_if_different > File > "/tmp/ansible_3VUnyg/ansible_modlib.zip/ansible/module_utils/basic.py", > line 1221, in set_mode_if_different > OSError: [Errno 30] Read-only file system: '/usr/bin/dumb-init' > fatal: [ansible.node-container]: FAILED! => { > "changed": false, > "failed": true, > "module_stderr": "Traceback (most recent call last):\n File > \"/tmp/ansible_3VUnyg/ansible_module_get_url.py\", line 573, in <module>\n > main()\n File \"/tmp/ansible_3VUnyg/ansible_module_get_url.py\", line > 459, in main\n changed = > module.set_fs_attributes_if_different(file_args, False)\n File > \"/tmp/ansible_3VUnyg/ansible_modlib.zip/ansible/module_utils/basic.py\", > line 1450, in set_fs_attributes_if_different\n File > \"/tmp/ansible_3VUnyg/ansible_modlib.zip/ansible/module_utils/basic.py\", > line 1221, in set_mode_if_different\nOSError: [Errno 30] Read-only file > system: '/usr/bin/dumb-init'\n", > "module_stdout": "", > "msg": "MODULE FAILURE", > "rc": 0 > } > to retry, use: --limit @/tmp/tmpegCroG/playbook.retry > PLAY RECAP > ********************************************************************* > ansible.node-container : ok=1 changed=0 unreachable=0 failed=1 > 2017-11-09T11:49:56.463302 Error applying role! [container.core] > caller_file=/_ansible/container/core.py caller_func=apply_role_to_container > caller_line=680 engine=<container.docker.engine.Engine object at > 0x7f5611f2a710> exit_code=2 playbook=[{'hosts': u'ansible.node-container', > 'roles': ['node_container'], 'vars': {}}] > 2017-11-09T11:49:56.468692 Playbook run finished > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/4bde0a32-0076-4baf-8be9-75ca30bda1eb%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/4bde0a32-0076-4baf-8be9-75ca30bda1eb%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Dick Visser GÉANT Want to join us? We're hiring: https://www.geant.org/jobs -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAL8fbwPCpohfbUxvmEEqCkhMOW8ZSudNLeLNEs4dK_OhL4FC_Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
