Ryan

> There is no need to change the existing code of act, other than make it to match github actions more closely  

> (with a flag or something to disable it by default)? if it will be useful for `act`, then I don't see why it would be under a flag.

> ```shell > act "pull_request" \ > -s DOCKER_USERNAME \ > -s DOCKER_PASSWORD > ``` Are you sure you don't input any whitespace or typo when asked for credentials?

> I didn't even get that far. See my "log excerpt". It should ask before running act at all ``` ~/void-pkgs (act)> act -s DOCKER_USERNAME Provide value for 'DOCKER_USERNAME': ```

these patterns are gitignore syntax, so you could just apply the reversed gitignore and walk through files https://github.com/nektos/act/blob/c802064975099a00c93b0c57f46b1e3964d33eef/pkg/container/docker_run.go#L579-L592

`podman` support is something I'm tracking but no idea when will that gets done. Feel free to submit PR if you have something done.

That may be the case for you but others can and will have more issues when trying to run `act` with `podman`. I don't recommend using `podman` right now unless...

> ``` > [build-test-release/build ] 🚀 Start image=catthehacker/ubuntu:act-latest > Error: Error response from daemon: unable to find a name and tag match for catthehacker/ubuntu in repotags: no such image >...

> 2\. `act` should create a `rw` container so we are allowed to write files into the filesystem. why?

> We are surely writing data into it, aren't we? Yes, but why we should do that? It works just fine in Docker Also, what is `rw` container?