Fake metdata.google.internal for GCP images with docker-compose

docker-compose.yml

version: "3"

services:
  metadata0:
    image: nginx:alpine
    volumes:
      - ./metadata-db0:/usr/share/nginx/html:ro
    command: [nginx-debug, '-g', 'daemon off;']

  db0:
    links:
      - metadata0:metadata.google.internal
    image: gcr.io/some-project/some_gcp_image:v1

  metadata1:
    image: nginx:alpine
    volumes:
      - ./metadata-db1:/usr/share/nginx/html:ro
    command: [nginx-debug, '-g', 'daemon off;']

  db1:
    links:
      - metadata1:metadata.google.internal
    image: gcr.io/some-project/some_gcp_image:v1

Sometimes you might want to spin up a few containers that are GCP aware and pull their config from metadata.google.internal.

This should be sufficient to get a static setup, but perhaps there are better ways that work with docker-compose scaling for example.