ospd-openvas exiting with code 132

Community Containers
1

I am running the latest version of the community containers and since the latest update ospd-openvas keeps exiting with error code 132
ospd-openvas-1 exited with code 0
ospd-openvas-1 exited with code 0
ospd-openvas-1 exited with code 0
ospd-openvas-1 exited with code 0
ospd-openvas-1 exited with code 132

I am hoping someone can provide some assistance, I am fairly new to docker and am struggling to find the cause of this.

2

Is anyone able to help me with this?

3

That usually means illegal instruction. Your CPU does not support the required instructions where the binary is complied with. I would suggest you re-compile it on the target platform.

4

Thanks, though was working before without an issue. It only stopped after I ran an update. Also how do I recompile? since this was something that I just used the Greenbone Community Containers - Greenbone Community Documentation to install…

5

You can check your CPU and upgrade to a supported version as well :wink:

6

Hi Lukas is there somewhere that this is documented - what CPU’s are supported? as the install documentation only has
Minimal:

CPU Cores: 2

Random-Access Memory: 4GB

Hard Disk: 20GB free

Recommended:

CPU Cores: 4

Random-Access Memory: 8GB

Hard Disk: 60GB free

As stated this was functioning prior to the latest update.

7

I am talking about opcode and CPU features and not Cores here … like amd64-avx etc …

8

Hi Lukas

Yes - that was what I was asking - since all that is in the install document is the above. So I will reword, is there are list of specific CPU features that are supported? Since this was working fine before and all other containers start without an issue.