Closed kuba-orlik closed 7 years ago
+1 I am able to repeat the issue too
The problem here is that the Docker container does not have permissions to
write to your ~/. mitmproxy. A simple hacky workaround is to chmod a+wr
your .mitmproxy folder. If you have a good - less hacky - solution, I'm
happy to include that in the docs. :)
On Mon, 29 Aug 2016, 14:06 Matthew Halpern, notifications@github.com wrote:
I am able to repeat the issue too
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/mitmproxy/docker-releases/issues/6#issuecomment-243256222, or mute the thread https://github.com/notifications/unsubscribe-auth/AA-NPtQ3PYxzGQzeEO-qm5OkDIpwyBtIks5qk0nBgaJpZM4JeeUm .
Fixed by #8. Thanks again, @maxcnunes! :smiley:
I'm trying to run
mitmproxy
with the following command:This is the output I get:
How can I fix it? :)