Even though that task is supposed to get a file and register (hence no `become: true` is required), I understand that it causes re-pulling an image w/ a diff user, which let the playbook fail while adding the following layer:
```
"Error:writing blob: adding layer with blob \"sha256:49a61133ba378a1ca5e8f77b3c05ed9980f80e89ff729db22a51bb524363e6a5\": processing tar file(write /usr/lib64/samba/libsmbd-base-samba4.so: no space left on device): exit status 1"
],
```
Having a `dev/mapper/vg-lv_home 1.2G 630M 555M 54% /home` is too small and not recommended (even for dev purposes), but we're going to investigate if running that single task with `become: true` (which doesn't hurt in this case) will solve the issue.
Even though that task is supposed to get a file and register (hence no `become: true` is required), I understand that it causes re-pulling an image w/ a diff user, which let the playbook fail while adding the following layer:
``` 49a61133ba378a1 ca5e8f77b3c05ed 9980f80e89ff729 db22a51bb524363 e6a5\": processing tar file(write /usr/lib64/ samba/libsmbd- base-samba4. so: no space left on device): exit status 1"
"Error:writing blob: adding layer with blob \"sha256:
],
```
Having a `dev/mapper/ vg-lv_home 1.2G 630M 555M 54% /home` is too small and not recommended (even for dev purposes), but we're going to investigate if running that single task with `become: true` (which doesn't hurt in this case) will solve the issue.