Local built catalogue container failed to load pictures of socks

[ghost]

Step to reproduce the problem:

1. Freshly clone catalogue and microservice-demo from github.
   git clone https://github.com/microservices-demo/microservices-demo.git
git clone https://github.com/microservices-demo/catalogue.git
2. Go to catalogue repo and run docker-compose build. If succeeded, the instruction will build image "weaveworksdemos/catalogue-dev:latest" and "weaveworksdemos/catalogue-dev-db:latest"
3. Go to microservices-demo repo and change file deploy/docker-compose/docker-compose.yml. We want to use local images instead of images in the hub. Replace "weaveworksdemos/catalogue" to "weaveworksdemos/catalogue-dev:latest", weaveworksdemos/catalogue-db to "weaveworksdemos/catalogue-dev-db:latest"
4. Run quickstart command docker-compose -f deploy/docker-compose/docker-compose.yml up -d in the microservices-demo repo
5. (IMPORTANT) Access the sock shop by using chrome incognito mode to prevent caching the photo. Every time you want to access the sock shop again, it's recommend to always close incognito window and access the shop in a new incognito window to prevent further caching.

Actual behavior:
All of the photos for the sock items cannot be accessed with a 404 not found error. Originally I didn't find this bug because at first, I used the default microservice-demo configuration and the browser startes to caching those images from that point. If I don't clean the cache, the sock shop will function normally even after I replace them with the local images (because of the browser caching).