← Back to context Comment by mkj 1 day ago How is docker a context switch overhead? It's the same processes running on the same kernel. 3 comments mkj Reply BirAdam 1 day ago You're adding all of the other supporting processes within the container that needn't be replicated. akdev1l 1 day ago It depends, you could have an application with something likeFROM scratchCOPY my-static-binary /my-static-binaryENTRYPOINT “/my-static-binary”Having multiple processes inside one container is a bit of an anti-pattern imo dnnddidiej 1 day ago Sidecars? Not in a simple app.
BirAdam 1 day ago You're adding all of the other supporting processes within the container that needn't be replicated. akdev1l 1 day ago It depends, you could have an application with something likeFROM scratchCOPY my-static-binary /my-static-binaryENTRYPOINT “/my-static-binary”Having multiple processes inside one container is a bit of an anti-pattern imo dnnddidiej 1 day ago Sidecars? Not in a simple app.
akdev1l 1 day ago It depends, you could have an application with something likeFROM scratchCOPY my-static-binary /my-static-binaryENTRYPOINT “/my-static-binary”Having multiple processes inside one container is a bit of an anti-pattern imo
You're adding all of the other supporting processes within the container that needn't be replicated.
It depends, you could have an application with something like
FROM scratch
COPY my-static-binary /my-static-binary
ENTRYPOINT “/my-static-binary”
Having multiple processes inside one container is a bit of an anti-pattern imo
Sidecars? Not in a simple app.