-
Notifications
You must be signed in to change notification settings - Fork 35
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
Debug docker image #2294
base: main
Are you sure you want to change the base?
Debug docker image #2294
Conversation
NOTE: This will work only for linux users and possibly not always duo to difference in libc versions. |
Hey, I worked on something like that before as well, maybe can be useful as reference https://github.com/restatedev/restate/pull/1913/files#diff-c619eafd655a2bbc0adc9b2b704c1f9ae253ccb77ddea1dd3de815ea6a8b9c62R1 Still everything is built within the container, but after the first time this will be super fast to build the next times. |
@slinkydeveloper Thank you for your input. I am wondering why your PR was never merged ? |
@muhamadazmy I never had time to finish it, and i didn't manage the enable the cache in CI, but locally it works fine! So it could be a good fit for |
Summary: While running the sdk-test-suite it was needed to rebuild the restate docker image multiple times which is very time consuming. Now by running `just debug-docker` a quick debug image will be made
@slinkydeveloper Thank you. I reused the docker file from your PR. It's better to also run the build inside a builder stage to avoid issues with libc. |
Debug docker image
Summary:
While running the sdk-test-suite it was needed to rebuild
the restate docker image multiple times which is very time
consuming.
Now by running
just debug-docker
a quick debug image willbe made (at least on second time)