-
I would like to collect coredumps from a C++ binary running inside a docker container in GitHub workflows in order to first print a backtrace immediately and second store it as an artifact (together with the binary) to debug later. I have set:
I’ve tried to set the path where core files are written:
but it fails because this is read only. Similarly, this doesn’t seem to have any effect:
In the default core dump location
is nothing to be found after a crash. From reading about this my guess is that the docker container would have to run with
in order to allow changing the path that but supposedly that’s not possible. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Maybe you can try using the syntax jobs.<job_id>.container.options to configure the optiones. For example:
|
Beta Was this translation helpful? Give feedback.
-
Awesome, I tested this and it works. Thank you! |
Beta Was this translation helpful? Give feedback.
@julianoes ,
Maybe you can try using the syntax jobs.<job_id>.container.options to configure the optiones.
For example: