Set seccomp to unconfined

[tolbrino]

The current dappnode package fails to start with the following error:

RuntimeError: can't start new thread

This suggests that the used Python has issues with the seccomp profile being used. This PR provides a quick workaround which made the package work for me again. A proper fix might involve checking out the installation of Python within the Docker image.

[mgarciate]

The current dappnode package fails to start with the following error:

RuntimeError: can't start new thread

This suggests that the used Python has issues with the seccomp profile being used. This PR provides a quick workaround which made the package work for me again. A proper fix might involve checking out the installation of Python within the Docker image.

security_opt: - seccomp:unconfined can have significant security implications.
According to chatgpt:

Security Implications
Increased Attack Surface:

Disabling seccomp removes protections against numerous types of attacks that could exploit vulnerabilities in system calls.
An attacker who gains access to the container can potentially perform a broader range of malicious actions, including attempts to escape the container and gain access to the host system.
Risk of Host Compromise:

With seccomp disabled, if the containerized application is compromised, an attacker could leverage unrestricted system calls to exploit kernel vulnerabilities, potentially leading to host compromise.
This is especially dangerous if the container runs with elevated privileges or has sensitive host mounts.
Non-Compliance with Security Best Practices:

Disabling seccomp goes against Docker's security best practices and industry standards for container security.
Regulatory and compliance standards may require the use of security mechanisms like seccomp.

@tolbrino Have you try to update docker at http://my.dappnode/system/advanced? I wouldn't set this parameter unless it's the last option

[kelsos]

We heard back from one of the users who encountered the same problem. They successfully managed to update docker despite getting errors in http://my.dappnode/system/advanced, it seems that it should work even if you get a check error.

After the update the user reported that they can use rotki normally, so updating docker should resolve the problem.

[tolbrino]

I will test this next as well.

[mgarciate]

I will test this next as well.

Let me know @tolbrino