4

Starting a docker postgresql container to dump a database using pg_dump to a mounted volume results in:

could not open output file "blah": protocol error

The protocol error is different from the permission denied issue as discussed here for instance. What does this error mean? There is no existing file in the mounted volume.

I'm using docker-machine on OSX.

Community
  • 1
  • 1
Berco Beute
  • 1,115
  • 15
  • 30
  • 1
    I had a similar problem in Windows. The filename had a timestamp with a colon in it, which is an illegal character in Windows. – reheated Mar 15 '16 at 12:01
  • You are right! I had the same issue with docker-machine on OSX. I'll update the answer. Thx! – Berco Beute Mar 15 '16 at 21:19

1 Answers1

1

Solved. It turned out my filename had a colon in it, which is not allowed with docker-machine on OSX. I initially thought it was a permission issue that can be solved by using starting the container in privileged model as described here.

Berco Beute
  • 1,115
  • 15
  • 30