Packer with an ansible-local provisions => Failed to set permissions on the temporary files error

[a...@sanger.ac.uk]

In my ansible file I have a few tasks where I need to become a user and install software as that user 

I have configured this as follows

- name: Install Linuxbrew

git:

repo: 'https://github.com/Linuxbrew/brew.git'

dest: '~{{ primary_user }}/.linuxbrew'

become: yes

become_user: '{{ primary_user }}'

become_flags: '-i'

become_method: sudo

However it errors saying that 

Failed to set permissions on the temporary files Ansible needs to create when becoming an unprivileged user

This is provisioned by packer as follows

    {

     "type": "ansible-local",

     "playbook_file": "ansible/assembly.yml"

   }

Other ansible commands operate fine but those with become: yes fail

Any advice much appreciated. Thanks

Anthony

[Rickard von Essen]

This is an common ansible problem (and Packer has nothing to do with it). Nevertheless read this:

https://docs.ansible.com/ansible/2.5/user_guide/become.html#becoming-an-unprivileged-user

Especially try to install the package including setfacl. 

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/packer/issues
IRC: #packer-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Packer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to packer-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/169c6bde-f235-4649-8f3c-a97a0f52153c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[a...@sanger.ac.uk]

Thanks for the reply.

I did see the ansible docs about unprivileged users but when I install the acl package I get a new error

sudo: no tty present and no askpass program specified

The reason I thought this may be packer related is that when I use the same playbook using vagrant provisioning in the same host background Ubuntu 18.04, I don't have these problems 

[Rickard von Essen]

Does your ssh_user have passwordless sudo? 

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/64763b26-a7da-428d-af98-94e65ba9dfc1%40googlegroups.com.

[a...@sanger.ac.uk]

I have 

      "ssh_username": "vagrant",

      "ssh_password": "vagrant",

in the packer json file and

# Add vagrant user to sudoers.

echo 'vagrant ALL=(ALL:ALL) NOPASSWD:ALL' > /etc/sudoers.d/vagrant

in a setup script

[Rickard von Essen]

I don't know if that susdoers syntax is correct. Try this:

vagrant ALL=(ALL) NOPASSWD: ALL

To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/5cafe21b-300c-46c3-9d4b-62efddd747a1%40googlegroups.com.

[Anthony Underwood]

I had your suggestion at first but when I changed it to

vagrant ALL=(ALL:ALL) NOPASSWD:ALL

it worked!! Thanks for your help