{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidfakwvt357tpkeifc7aq5ay7qr25ntdcbvhwv56losnkzlpe5zga",
    "uri": "at://did:plc:hwpfviglvxef74s5w4fhywt7/app.bsky.feed.post/3mdtesjii2ux3"
  },
  "contributors": [
    {
      "did": "did:plc:dqehxkfb3kv6bx7tfkvyzdt4",
      "role": "author"
    }
  ],
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreie7g3o227ymxxixljmjliz53sx4jedliljrwn3snuxzdt7y4kyyoy"
    },
    "mimeType": "image/png",
    "size": 4687
  },
  "description": "One thing that always confuses me with Docker is how exactly mounting volumes behaves. At a basic level it’s fairly straight forward: you declare a volume in a Dockerfile, and then either explicitly mount something there or docker automatically creates an anonymous volume for you. Done. But it turns out there’s quite a few edge cases… Changing ownership of the folder Perhaps the...",
  "path": "/understanding-docker-volume-mounts/",
  "publishedAt": "2019-04-01T00:00:00Z",
  "site": "at://did:plc:hwpfviglvxef74s5w4fhywt7/site.standard.publication/3mnmr7tmggs2e",
  "title": "Understanding Docker volume mounts"
}