{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://inquir.org/#organization","name":"Inquir","url":"https://inquir.org","logo":{"@type":"ImageObject","url":"https://inquir.org/favicon.png","width":256,"height":256}},{"@type":"WebSite","@id":"https://inquir.org/#website","name":"Inquir Compute","url":"https://inquir.org","inLanguage":["en","ru"],"publisher":{"@id":"https://inquir.org/#organization"}},{"@type":"WebPage","@id":"https://inquir.org/features/container-runtime#webpage","url":"https://inquir.org/features/container-runtime","name":"Container runtime for serverless functions","headline":"Container runtime for serverless functions","description":"Per-function containers for Node.js, Python, and Go: dependencies per function, a POSIX-friendly filesystem view, and smaller blast radius than a shared multitenant interpreter.","inLanguage":"en-US","isPartOf":{"@id":"https://inquir.org/#website"},"breadcrumb":{"@id":"https://inquir.org/features/container-runtime#breadcrumb"},"author":{"@id":"https://inquir.org/#organization"},"datePublished":"2025-11-01T00:00:00.000Z","dateModified":"2026-06-23T00:00:00.000Z","citation":{"@type":"CreativeWork","url":"https://inquir.org/docs"}},{"@type":"BreadcrumbList","@id":"https://inquir.org/features/container-runtime#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://inquir.org/"},{"@type":"ListItem","position":2,"name":"Features","item":"https://inquir.org/features"},{"@type":"ListItem","position":3,"name":"Container runtime","item":"https://inquir.org/features/container-runtime"}]},{"@type":"TechArticle","@id":"https://inquir.org/features/container-runtime#article","headline":"Container runtime for serverless functions","description":"Per-function containers for Node.js, Python, and Go: dependencies per function, a POSIX-friendly filesystem view, and smaller blast radius than a shared multitenant interpreter.","image":"https://inquir.org/opengraph-image.png","inLanguage":"en-US","author":{"@id":"https://inquir.org/#organization"},"publisher":{"@id":"https://inquir.org/#organization"},"datePublished":"2025-11-01T00:00:00.000Z","dateModified":"2026-06-23T00:00:00.000Z","isPartOf":{"@id":"https://inquir.org/features/container-runtime#webpage"}},{"@type":"FAQPage","@id":"https://inquir.org/features/container-runtime#faq","url":"https://inquir.org/features/container-runtime","isPartOf":{"@id":"https://inquir.org/features/container-runtime#webpage"},"mainEntity":[{"@type":"Question","name":"Can functions read and write local disk?","acceptedAnswer":{"@type":"Answer","text":"Treat filesystems inside containers as ephemeral unless your deployment explicitly documents durable volumes; persist user data to external stores."}},{"@type":"Question","name":"How does container isolation help security reviews?","acceptedAnswer":{"@type":"Answer","text":"Separate processes and file systems per function reduce blast radius compared to one shared interpreter serving unrelated routes."}},{"@type":"Question","name":"Does every function need its own container image?","acceptedAnswer":{"@type":"Answer","text":"Each function carries its own dependency closure; that trades a bit of overhead for reproducible deploys and fewer “works on the server” surprises."}}]}]}