-
Notifications
You must be signed in to change notification settings - Fork 23
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
Updating Codegen Docker Images and Storage on Dockerhub #550
Comments
@soaapp The latest and 1.6.32 has have been released to the docker hub. Please double-check after the 1.6.33 release at the end of the month to ensure that the light-bot build will release the new version for each 1.6.x release. Thanks. Let's close the issue when we see the 1.6.33 release on the docker hub. |
@stevehu I believe the 1.6.33 release was completed at the end of March but it seems the light-bot did not release for each 1.6.x. If possible, the docker image creation for 1.6.26 is required. Thank you for your help. |
Here is the 1.6.33 released by the light-bot several days ago. We cannot release something with a previous tag by light-bot. I am wondering if you could upgrade your tutorial with 1.6.33 tag. |
It currently need 1.6.26 as that is the versioning we support for it. Is there anyway that image can be added as well? |
@soaapp I checked the Dockerfile and it uses the latest code from the 1.6.x branch, not from the tag. We cannot go back to the time to build the docker image without a customized Dockerfile to do so. https://github.com/networknt/light-docker/blob/1.6.x/light-codegen/Dockerfile#L9 If you look at the 1.6.26 release, we do have the codegen-cli.jar attached. You can use that jar file to build a customized docker image and publish it to your internal docker registry. If you want to publish to the public docker hub, please submit a PR in the light-docker and I can run it to publish to networknt. https://github.com/networknt/light-codegen/releases/tag/1.6.26 |
Resume the creation of codgen docker images and storage on dockerhub
The text was updated successfully, but these errors were encountered: