aarm64 run issues on RPI4 8gb.

[Phalen]

I have been attempting to get fipa server running on an 8gb pi4 with no success. so far the docker system has been the closest i could find but even that errors on running.

1. cant detect memory. the python script has no way to handle checking free/total mem on the pi. I edited the script to fudge it with static files saying it was good.
2. when it gets to the part about crony it errors due to lack of systemd regardless of choosing to use ntp or not. I got a bit frustrated and due to lack of knowledge stopped here to see if it can get properly fixed for the pi's I am sure many small businesses would love to use this system if it works on a pi for a wide range of use cases as well as home users.

I am using the pi firmware and a regular install of ubuntu lts i believe 20.04 please let me know what things are needed to debug.

[rjeffman]

Hello,

On Thu, Feb 10, 2022 at 1:56 AM Phalen ***@***.***> wrote: I have been attempting to get fipa server running on an 8gb pi4 with no success. so far the docker system has been the closest i could find but even that errors on running. 1. cant detect memory. the python script has no way to handle checking free/total mem on the pi. I edited the script to fudge it with static files saying it was good. 2. when it gets to the part about crony it errors due to lack of systemd regardless of choosing to use ntp or not. I got a bit frustrated and due to lack of knowledge stopped here to see if it can get properly fixed for the pi's I am sure many small businesses would love to use this system if it works on a pi for a wide range of use cases as well as home users. I am using the pi firmware and a regular install of ubuntu lts i believe 20.04 please let me know what things are needed to debug. — Reply to this email directly, view it on GitHub <#445>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANCS4FBOT55VRPHTFWCUVMDU2NAQ7ANCNFSM5N7SCF5A> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

I've been using FreeIPA on a Raspberry Pi 4 8Gb, for a while now, but I'm using Fedora 35, not Ubuntu. And I'm not using the Docker container, with which I don't have any experience with. If you haven't done so, please, check FreeIPA server container docs: https://github.com/freeipa/freeipa-container There are some tips on debugging issues. HTH, Rafael

…

-- Rafael Guterres Jeffman Senior Software Engineer FreeIPA - Red Hat

[adelton]

Besides the pointer to the debugging information that @rjeffman provided, it would be also helpful to state what image (based on which OS version) you tried, and what issues you got exactly, including traceback in the ipa-server-install output and in the logs.

Overall it seems you might be hitting some general issue with running systemd in containers under docker which was also discussed in #429, not something specific to Raspberry or to ARM. You might want to try podman to see if you get further along.

[Phalen]

thank you both for the suggestions. I had been shying away from redhat products since they started making poor decisions like removing the most popular sas controllers out there which caused me a good deal of pain when working with openstack and maas images.

I am precisely hitting issues as listed in #429 sadly my search foo did not work in finding that. Since that rpi will only be hosting freeipa cgroups1 will be a fine option for me untill the next lts ubuntu so i can get working podman on it.