Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

publish container images for the other interpreters #100

Open
codefromthecrypt opened this issue Apr 29, 2023 · 0 comments
Open

publish container images for the other interpreters #100

codefromthecrypt opened this issue Apr 29, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@codefromthecrypt
Copy link

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

@codefromthecrypt codefromthecrypt added the enhancement New feature or request label Apr 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant