Request: make a Docker image that is compatible with ARM devices #2648
Comments
|
That bus error looks like this bootsnap issue, there are a few mitigations in that thread. |
|
@Travis42 were you able to resolve this? It's so bad that there is no easy way to install huginn on some powerful arm based SBCs these days. |
|
@ch40s I tried all sorts of options over a 2 week period. Never got Huginn to work on an ARM device, as there was always some dependency to compile that I couldn't make work, despite advice. I messed with different versions of dependencies such as libv8, mini_racer, nokogiri, devise, bcrypt, etc. I did my best to cut out bootsnap. I think it was the rake dependency on bcrypt that finally made me call it a wash for ARM. Aside: I did manage to get the docker image working on a digital ocean droplet (easily). The problem there is that once you have it running, there is no user created within the docker image. I'm not very savvy with Docker, so that was another dead end as I tried to figure out the chicken or egg game there with modifying configuration files, setting up SSL, etc. I came at it from the Docker angle, as well as regular install attempts paired with CapRover and Yunohost. For the former, I couldn't edit/configure. For the latter two, I couldn't get the install of Huginn or Docker container version to play nice. I admit defeat. |
|
@Travis42 I totally agree with you! Pretty disappointing. Would you be willing to share your arm docker image for testing purposes? |
|
I don't have an ARM docker image, sorry. What I was referring to was the
docker image that they have as part of this project (huginn/huginn). It
runs on a x86 architecture.
…On Wed, Jan 1, 2020 at 10:22 AM CS ***@***.***> wrote:
@Travis42 <https://github.com/Travis42> I totally agree with you! Pretty
disappointing. Would you be willing to share your arm docker image for
testing purposes?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2648?email_source=notifications&email_token=ABZ3D6YOAH3LPIVKVRXQEN3Q3TGL3A5CNFSM4J3B5M2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH5JAQI#issuecomment-570069057>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABZ3D6YWEOEIMVGTEAGHLCLQ3TGL3ANCNFSM4J3B5M2A>
.
|
|
Just wanted to add so that the devs know there are more than two people interested in arm installs/dockers. Same as Travis42 but even more masochistic in that I'm now about 3 weeks in. I can only take so much before I give up. The rpi4 is the PERFECT board for Huginn. 4 cores and 4gb RAM, set it up mostly headless and leave it to run on 7w electricity in a cold corner somewhere. It has also been out since last... June? I'd be willing to lend a hand if someone who knows the project can hand hold. If not then I'm not sure I want to set this up on my daily driver laptop, already too many things going on on it. |
|
Yes, another armhf Raspberry Pi user here. Interested to be able to put Huginn on a Pi via Docker also. |
|
I used the Docker from the Ubuntu's repository (Docker's repo doesn't work) and after I executed the line to run the container I got on console: |
|
Please have a look at #2563. I run Huginn on Docker on a Raspberry Pi 4. Unfortunately, I still use an |
|
Hi! I'm very interesting in install docker in rasp 4. |
My reactions had nothing to do with you mentioning another project. In my mind there are no "competitors" in non commercialized open source. Nobody gains or looses anything from a user or non-user.
I know that sucks, but that is also open source. If nobody cares about it enough to work on on a problem noone else gets the feature or the support. To me your posts sound like they have the intention to pressure contributors and maintainers into something. Everybody is doing this in their free time and the license literally says you get what you get or what you make of it. In my experience complaining or finger pointing never got anyone to do anything in open source. I am personally not interested in running Huginn on ARM but would love to see contributions that enable it. |
|
Hey there, I tried pulling and running a image to run on my Raspberry Pi 4 and I noticed it's only x86 right? |
|
Do we have already a functional docker image for arm? |
|
this is a joke, ARM processors are the standard by now and project like these, even if they are open source, should support ARM |
I didn't get the punchline, is it supposed to be a joke about ARM or open source software? |
Completly agree. Tried setting it up on my SBC and it was hell, never worked properly. |
|
I found this image somebody else made for ARM and have been using it on an RPI4 4gb to good effect. |
This image was built by me, but the merit belongs to @sfischer13 because of his Huginn armhf branches. |
|
Hi! I have forget something? System InformationRaspberry Pi 4 Model B Rev 1.2 Linux raspberrypi 5.10.52-v7l+ #1441 SMP Tue Aug 3 18:11:56 BST 2021 armv7l GNU/Linux |
Late reply but in case you haven't figured it out already you're running armv7 which is 32bit. Like the error says you need to be running an arm64 OS. There's 64bit Raspbian builds available here and I think Ubuntu also has 64 bit arm build available |
|
I just created a Docker image of Huginn single process compatible with ARMv7/armhf, ARMv8/aarch64 and intel x86. This image is automatically updated for every new commit on https://github.com/huginn/huginn. I have no plans to support the multiple processes docker image of Huginn because I don't use it myself, and it is more difficult to build. |
|
@unixfox funny seeing you here, I use your ARM nitter image :D |
Add setup-qemu and setup-buildx actions to give docker the ability to build multiple architecture builds Remove call to `./build_docker_image.sh` Replace docker build script with build-push action from docker. Add basic metadata tagging. REF: huginn#2648
* Add setup-qemu and setup-buildx actions to give docker the ability to build multiple architecture builds * Remove call to `./build_docker_image.sh` * Replace docker build script with build-push action from docker. * Add basic metadata tagging. REF: huginn#2648
|
When will the ARM docker image support be available? |
For someone stumbling upon this, this image is the only thing here that works, at least by my experience. |
After a 2 day long battle with dependency hell and compiling from source for my Raspberry Pi, then trying the docker image route only to realize that there is no ARM image...I'm ready to give up.
Here's my rough journey on the local install/compile side, if you're curious:
Steps to get Huginn to work on Raspi:
#2299
https://github.com/huginn/huginn/wiki/Novice-setup-guide
sudo apt-get install libmariadb-dev mysql-client mysql-common mysql-server
cp .env.example .env
change versions in Gemfile
update Gemfile.lock by doing:
for nokogiri (it has to compile from source on a raspberry pi:
'devise' also has to compile, requires bcrypt
mysql2 error
bundle exec rake db:create
Massive error readout follows, but here are the probable important bits:
WARNING: description and summary are identical
WARNING: See http://guides.rubygems.org/specification-reference/ for help
WARNING: description and summary are identical
WARNING: open-ended dependency on spring (>= 0, development) is not recommended
if spring is semantically versioned, use:
add_development_dependency 'spring', '~> 0'
WARNING: See http://guides.rubygems.org/specification-reference/ for help
WARNING: description and summary are identical
WARNING: See http://guides.rubygems.org/specification-reference/ for help
WARNING: description and summary are identical
WARNING: open-ended dependency on spring (>= 0, development) is not recommended
if spring is semantically versioned, use:
add_development_dependency 'spring', '~> 0'
WARNING: See http://guides.rubygems.org/specification-reference/ for help
/var/lib/gems/2.3.0/gems/bootsnap-1.4.5/lib/bootsnap/compile_cache/iseq.rb:18: [BUG] Bus Error at 0x15577e2
ruby 2.3.3p222 (2016-11-21) [arm-linux-gnueabihf]
...
-- Control frame information -----------------------------------------------
(ton of stuff)
...
-- Ruby level backtrace information ---------------------------------------
(ton of stuff)
...
-- Other runtime information -----------------------------------------------
(ton of stuff)
Loaded script: /usr/local/bin/rake
Loaded features:
...
Process memory map:
...
[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
The text was updated successfully, but these errors were encountered: