the stack created but the docker it self restarts constantly

[sojab0on]

Hi I managed to create the stack based on teh compose file and it ran corectly but the docker cosntantly restarts with only this in the logs tandard_init_linux.go:239: exec user process caused: exec format error

How can i fix that this is beeing run on docker on a aarch64 pi4

[sojab0on]

Also tried to do it on an linux x86 host /usr/lib/python3/dist-packages/supervisor/options.py:474: UserWarning: Supervisord is running as root and it is searching for its configuration file in default locations (including its current working directory); you probably want to specify a "-c" argument specifying an absolute path to a configuration file for improved security. self.warnings.warn( 2024-08-09 09:18:14,724 INFO Set uid to user 0 succeeded 2024-08-09 09:18:14,731 INFO supervisord started with pid 1 2024-08-09 09:18:15,733 INFO spawned: 'set_root_password' with pid 8 2024-08-09 09:18:15,736 INFO spawned: 'corosync-qnetd' with pid 9 2024-08-09 09:18:15,740 INFO spawned: 'sshd' with pid 10 2024-08-09 09:18:15,745 INFO success: set_root_password entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-08-09 09:18:15,751 WARN exited: corosync-qnetd (exit status 1; not expected) 2024-08-09 09:18:15,806 WARN exited: sshd (exit status 255; not expected) 2024-08-09 09:18:15,880 INFO exited: set_root_password (exit status 0; expected) 2024-08-09 09:18:16,883 INFO spawned: 'corosync-qnetd' with pid 15 2024-08-09 09:18:16,886 INFO spawned: 'sshd' with pid 16 2024-08-09 09:18:16,900 WARN exited: corosync-qnetd (exit status 1; not expected) 2024-08-09 09:18:16,952 WARN exited: sshd (exit status 255; not expected) 2024-08-09 09:18:18,956 INFO spawned: 'corosync-qnetd' with pid 17 2024-08-09 09:18:18,959 INFO spawned: 'sshd' with pid 18 2024-08-09 09:18:18,970 WARN exited: corosync-qnetd (exit status 1; not expected) 2024-08-09 09:18:19,025 WARN exited: sshd (exit status 255; not expected) 2024-08-09 09:18:22,031 INFO spawned: 'corosync-qnetd' with pid 19 2024-08-09 09:18:22,034 INFO spawned: 'sshd' with pid 20 2024-08-09 09:18:22,045 WARN exited: corosync-qnetd (exit status 1; not expected) 2024-08-09 09:18:22,096 INFO gave up: corosync-qnetd entered FATAL state, too many start retries too quickly 2024-08-09 09:18:22,098 WARN exited: sshd (exit status 255; not expected) 2024-08-09 09:18:23,100 INFO gave up: sshd entered FATAL state, too many start retries too quickly then log constantly spits back that

[bcleonard]

I run this on a x86 virtual instance, so there was never any need to test on a raspberry pi.

When I see the errors you listed above, that usually means the processes in the container don't have the correct permissions to write to where you mounted /etc/corosync from.

It looks like somebody did get it working on arm: arm suport

[sojab0on]

Also installed in on a synology nas with docker engine but there it constantly spits out this This is a Intel Atom based device X86_64 with 8gb ram

2024-08-15 06:22:06,610 INFO spawned: 'corosync-qnetd' with pid 16 2024-08-15 06:22:06,614 INFO spawned: 'sshd' with pid 17 2024-08-15 06:22:06,625 WARN exited: corosync-qnetd (exit status 1; not expected) 2024-08-15 06:22:06,680 WARN exited: sshd (exit status 255; not expected) 2024-08-15 06:22:09,685 INFO spawned: 'corosync-qnetd' with pid 18 2024-08-15 06:22:09,688 INFO spawned: 'sshd' with pid 19 2024-08-15 06:22:09,699 WARN exited: corosync-qnetd (exit status 1; not expected) 2024-08-15 06:22:09,750 INFO gave up: corosync-qnetd entered FATAL state, too many start retries too quickly 2024-08-15 06:22:09,751 WARN exited: sshd (exit status 255; not expected) 2024-08-15 06:22:10,752 INFO gave up: sshd entered FATAL state, too many start retries too quickly

cant seem to find out why it was a clean image pull

[nakedgoat]

FYI, doing the same thing for me - proxmox-qdevice | 2024-10-27 20:13:16,442 INFO Set uid to user 0 succeeded proxmox-qdevice | 2024-10-27 20:13:16,454 INFO supervisord started with pid 1 proxmox-qdevice | 2024-10-27 20:13:17,464 INFO spawned: 'set_root_password' with pid 7 proxmox-qdevice | 2024-10-27 20:13:17,475 INFO spawned: 'corosync-qnetd' with pid 8 proxmox-qdevice | 2024-10-27 20:13:17,486 INFO spawned: 'sshd' with pid 9 proxmox-qdevice | 2024-10-27 20:13:17,492 INFO success: set_root_password entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) proxmox-qdevice | 2024-10-27 20:13:17,514 WARN exited: corosync-qnetd (exit status 1; not expected) proxmox-qdevice | 2024-10-27 20:13:17,627 INFO exited: set_root_password (exit status 0; expected) proxmox-qdevice | 2024-10-27 20:13:18,637 INFO spawned: 'corosync-qnetd' with pid 14 proxmox-qdevice | 2024-10-27 20:13:18,639 INFO success: sshd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) proxmox-qdevice | 2024-10-27 20:13:18,660 WARN exited: corosync-qnetd (exit status 1; not expected) proxmox-qdevice | 2024-10-27 20:13:20,672 INFO spawned: 'corosync-qnetd' with pid 15 proxmox-qdevice | 2024-10-27 20:13:20,698 WARN exited: corosync-qnetd (exit status 1; not expected) proxmox-qdevice | 2024-10-27 20:13:23,746 INFO spawned: 'corosync-qnetd' with pid 16 proxmox-qdevice | 2024-10-27 20:13:23,782 WARN exited: corosync-qnetd (exit status 1; not expected) proxmox-qdevice | 2024-10-27 20:13:24,786 INFO gave up: corosync-qnetd entered FATAL state, too many start retries too quickly - anyone find a fix, or a different solution?

[bcleonard]

As stated previously, these types of errors are related to one of three items:

1) wrong arch 2) insufficent permissions 3) port 22 blocked

I can only test this on an x86_64 device.

[github-actions[bot]]

This issue is stale because it has been open for 30 days with no activity.