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
Is your feature request related to a problem? Please describe.
The python image is great, as interpreters can be a base layer a user can FROM to add their scripts and change the CMD (or worst case ENTRYPOINT). This takes the best of docker/OCI as you can cache the base layer and also know it is in use (vs knowing nothing about the python under if the wasm is repackaged).
Can you please publish OCI image packages for the other interpreters?
Describe the solution you'd like
packages like ghcr.io/vmware-labs/python-wasm:3.11.3 for php, ruby and any other interpreter handled in the future here.
Describe alternatives you've considered
stick with wasm, except it doesn't explain a clean way of dealing with layers. Basically the end user must be able to control the host runtime to change mounts, or at least be able to affect them. However, the host may not want to expose that. It is cleaner to allow OCI as the whole thing can be configured and validated easier.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The python image is great, as interpreters can be a base layer a user can FROM to add their scripts and change the CMD (or worst case ENTRYPOINT). This takes the best of docker/OCI as you can cache the base layer and also know it is in use (vs knowing nothing about the python under if the wasm is repackaged).
Can you please publish OCI image packages for the other interpreters?
Describe the solution you'd like
packages like ghcr.io/vmware-labs/python-wasm:3.11.3 for php, ruby and any other interpreter handled in the future here.
Describe alternatives you've considered
stick with wasm, except it doesn't explain a clean way of dealing with layers. Basically the end user must be able to control the host runtime to change mounts, or at least be able to affect them. However, the host may not want to expose that. It is cleaner to allow OCI as the whole thing can be configured and validated easier.
Additional context
No response
The text was updated successfully, but these errors were encountered: