John Miller

I'm seeing the same behavior, and I'm hitting the container directly over port 8080 - also in docker. I had used a pervious version and it worked fine with this...