This message was deleted.

I didn't use egress till now but as a hint , did you run docker and container as root ? it seems like permission issue...

In the latest egress version, we switched from running as root to a created

egress

user in order to use sandboxing with chrome. I'm sure that's related, but I still need to find a way to reproduce it (it works on our Linux servers and on Macbooks)

I'm just docker rmi image egress -f and pull newest docker image on three another machines. And I tried to run docker by superuser - no effect