-
Notifications
You must be signed in to change notification settings - Fork 157
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
Finalize docker export capabilities #4
Comments
Hi. I'm using this Opyrator well, and want to deploy my project in a Docker image. So I tried the command line as you noticed |
@dleunji the Docker export is not ready yet for release :( But we have prioritized this feature and will update this issue as soon as it is ready for usage. |
Hi, I want to collaborate on this issue, can you tell me if the logic for exporting the docker would be acceptable?
|
Hey @amitmtrn, thanks for your thoughts! I think this looks like a good approach and looks like it would be worth trying out :) In the future we could discuss whether it could be better to have an official opyrator image (step 2) instead of using the python base image. |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 14 days |
Any updates on this, please? |
Feature description:
Finalize capabilities to export an opyrator to a Docker image.
The export can be executed via command line:
opyrator export my_opyrator:hello_world --format=docker my-opyrator-image:latest
💡 The Docker export requires that Docker is installed on your machine.
After the successful export, the Docker image can be run as shown below:
Running your Opyrator within this Docker image has the advantage that only a single port is required to be exposed. The separation between UI and API is done via URL paths:
http://localhost:8080/api
(API);http://localhost:8080/ui
(UI). The UI is automatically configured to use the API for all function calls.The text was updated successfully, but these errors were encountered: