Look up what DevToolsActivePort is, and figure out why chromedriver can't connect to it.
The lack of output from "docker port pricer" tells me that the port still isn't being forwarded from your MacOS localhost:2222 -> Container ssh:22, so you'll have to fix that.
Looks like docker isn't forwarding the port, so you'll have to recreate the container from the dev image you built, and set up port forwarding correctly. The playbook should do this automatically.
The issue is that you're using the docker_container module here:
What happens when you re-run the playbook with -vvv?
The issue here is that although your MacOS system is listening on port 22 (SSH), Ansible needs to connect to the docker container, which is available via port 2222, as per this line here:
An important tool for troubleshooting the docker container restart with systemd is to run ansible in check mode like this:
You also have to add a play to install the chromium-chromedriver and chromium-browser packages.
The underlying issue is that the ansible playbook isn't complete, and the play on this line needs to be troubleshot so the container starts back up with systemd, so snap will run:
Note that status code 127 is usually used by bash and bash-like shells to indicate that the command was not found. You can access the return code (status code) from the $? variable on both Unix and Windows.
Karen fixed this in this commit: