I was having the same problem. I noticed the images are read from a resource named:

_next/image?url=<path_to_image>

I'm running this from a docker container, and restarting the docker container was enough to regenerate the server cache.