You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The copa patch command should complete successfully without crashing, applying necessary patches to the specified Docker image.
Actual Behavior
The command fails with a segmentation fault specifically when executed within GitLab CI. The error does not occur when the command is executed in a local Docker container. Below is the error output captured from the GitLab CI job:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xc4832f]
goroutine 51 [running]:
github.com/cpuguy83/go-docker/transport.(*Transport).DoRaw(...)
...
created by google.golang.org/grpc.(*acBalancerWrapper).Connect in goroutine 50
...
Interestingly, the same command executes successfully when run locally in a Docker container, indicating that the issue may be specific to the GitLab CI environment.
Steps To Reproduce
Pull any Docker image within a GitLab CI job.
Execute a vulnerability scan on the image using Trivy within the same CI job.
Attempt to patch the image using copa patch within the GitLab CI job.
Version of copa
v0.9.0
Expected Behavior
The
copa patch
command should complete successfully without crashing, applying necessary patches to the specified Docker image.Actual Behavior
The command fails with a segmentation fault specifically when executed within GitLab CI. The error does not occur when the command is executed in a local Docker container. Below is the error output captured from the GitLab CI job:
Interestingly, the same command executes successfully when run locally in a Docker container, indicating that the issue may be specific to the GitLab CI environment.
Steps To Reproduce
copa patch
within the GitLab CI job.Commands Executed:
Dockerfile
Are you willing to submit PRs to contribute to this bug fix?
The text was updated successfully, but these errors were encountered: