You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when a user runs e2b build we upload the Docker context to our backend and build the image there.
This bring several drawbacks like slowness, bad DX because we don't support multi-stage builds or private images, and requirement from us to manage this whole service.
Instead, we should let users to build their images locally (or in CI).
We would have two commands (naming can change):
e2b build - builds the image locally and pushes it to our backend
e2b push <docker-image-specifier>- pushes the image to our backend
The text was updated successfully, but these errors were encountered:
Currently, when a user runs
e2b build
we upload the Docker context to our backend and build the image there.This bring several drawbacks like slowness, bad DX because we don't support multi-stage builds or private images, and requirement from us to manage this whole service.
Instead, we should let users to build their images locally (or in CI).
We would have two commands (naming can change):
e2b build
- builds the image locally and pushes it to our backende2b push <docker-image-specifier>
- pushes the image to our backendThe text was updated successfully, but these errors were encountered: