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
Hey, the latest Rocketpool image does not work for me anymore. I'm on a up-to-date dappnode and I get the following error when the container tries to start:
[ INFO ] supervisord start
2024-08-11 11:46:55,450 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
2024-08-11 11:46:55,452 INFO supervisord started with pid 1
2024-08-11 11:46:56,454 INFO spawned: 'quit_on_failure' with pid 7
2024-08-11 11:46:56,456 INFO spawned: 'api_00' with pid 8
2024-08-11 11:46:56,457 INFO spawned: 'nginx' with pid 9
2024-08-11 11:46:56,458 INFO spawned: 'rocketpool' with pid 10
2024-08-11 11:46:56,458 INFO success: api_00 entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
Mainnet network
[ INFO-rocketpool ] set-password
runtime/cgo: pthread_create failed: Operation not permitted
SIGABRT: abort
PC=0x7f5e474afe2c m=0 sigcode=18446744073709551610
goroutine 0 [idle]:
runtime: g 0: unknown pc 0x7f5e474afe2c
stack: frame={sp:0x7ffeb93220c0, fp:0x0} stack=[0x7ffeb8b23550,0x7ffeb9322560)
Describe the bug
Hey, the latest Rocketpool image does not work for me anymore. I'm on a up-to-date dappnode and I get the following error when the container tries to start:
DAppNode version:
Core DAppNode Packages versions
bind.dnp.dappnode.eth: 0.2.11
core.dnp.dappnode.eth: 0.2.96
dappmanager.dnp.dappnode.eth: 0.2.90, commit: df351d59
https.dnp.dappnode.eth: 0.2.2
ipfs.dnp.dappnode.eth: 0.2.23
vpn.dnp.dappnode.eth:
wifi.dnp.dappnode.eth: 0.2.9
System info
dockerComposeVersion: 1.25.5
dockerServerVersion: 20.10.6
dockerCliVersion: 20.10.6
os: debian
versionCodename: bullseye
architecture: amd64
kernel: 5.10.0-9-amd64
Disk usage: 64%
The text was updated successfully, but these errors were encountered: