Merge pull request #57 from TomasTomecek/0.4.0-release

0.4.0 release

CHANGELOG.md

@@ -1,3 +1,25 @@
+# 0.4.0
+Ansible-bender now uses Azure Pipelines as a CI system.
+
+## Features
+* There were updates to documentation in README:
+  * Info about vfs and overlay buildah storage backends.
+  * Rootless containers.
+  * How you can use base images with python2.
+  * Requirements of ansible-bender.
+* Bender now produces a more clear message when a base image doesn't have a
+  python interpreter.
+* You are now able to pass path to the python interpreter inside the base image
+  via CLI.
+
+## Bug fixes
+
+* Bender now uses more buildah commands instead of podman.
+* If bender is invoked with a non-root user, the ansible-playbook session is
+  now wrapped with `buildah unshare`.
+* Don't print to error log when an image is being pulled.
+
+
 # 0.3.2
 
 I experimented with running ansible-bender inside an OpenShift pod. Details can

README.md

@@ -287,13 +287,10 @@ If you are familiar with podman and buildah, you know that you can
 these tools. Ansible-bender doesn't change this configuration in any way so
 it's up to you how you set up buildah and podman. The same applies for running
 ansible-bender as root or not: buildah allows you to utilize rootless
-containers. The only problem is that Ansible [is not
-able](https://github.com/ansible/ansible/issues/50583) to interact with
-rootless buildah containers when they are backed up by an overlay storage
-backend.
+containers.
 
-My suggestion is to run ansible-bender as root using the overlay storage
-backend. Vfs backend is slow and inefficient.
+My suggestion is to use the overlay storage backend. Vfs backend is slow and
+inefficient.
 
 
 ### Caching mechanism