deepfence / deepfence/ThreatMapper

Vulnerability scan signal:killed error

Open
#2,287 1 comment 0 reactions 0 assignees View on GitHub
bug needs-triage
Dominant language
TypeScript
Stars
5.3k
Forks
631
PR merge metrics
No merged PRs in 30d

Description

**Describe the issue**
Running a scan on this specific Ubuntu 22.04 host is always giving an error.

**Expected behavior**
Expecting scan to complete successfully.

**Screenshots**
![image](https://github.com/user-attachments/assets/8fd34128-94be-48f1-aef2-427d1546d9e3)

![image](https://github.com/user-attachments/assets/abcc964a-8ebc-4b8d-b58e-471eeb618c8d)

**Components/Services affected**
- [X] UI/Frontend

[deepfence-agent-logs-dev-ien-ca-2024-08-15-09-37-08.zip](https://github.com/user-attachments/files/16624274/deepfence-agent-logs-dev-ien-ca-2024-08-15-09-37-08.zip)
[deepfence-console-logs-2024-08-15-09-36-56.zip](https://github.com/user-attachments/files/16624275/deepfence-console-logs-2024-08-15-09-36-56.zip)

**Additional context**
Console and agent logs attached.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the attached deepfence-agent and deepfence-console logs, then reproduce the vulnerability scan on the specified Ubuntu 22.04 host. Done means the scan completes successfully without the signal:killed error.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.