troubles installing Hyku

[Michele Nesi]

Hallo all,
I'd like to try Hyku for some photographic collections of my University, but I've troubles installing it with Docker compose.
Strangely I've not found a comprehensive installation guide, could you point it to me please?
I cloned the repository with
git clone https://github.com/samvera/hyku.git
and ran
docker compose up
but the installation crashes with this error:
hyku-initialize_app-1 | rails aborted!
hyku-initialize_app-1 | Errno::EACCES: Permission denied @ rb_sysopen -
...
I tried (following this official guide https://github.com/samvera/hyku#with-docker) with
docker compose up web
crushes

with
docker compose -f docker-compose.yml -f docker-compose.override-nodory.yml up
don't work...
it says
! base The requested image's platform (linux/arm64) does not match the detected host platform (linux/amd64/v3) and no specific platform was requested
I don't understand if it's serious...

and with
docker compose -f docker-compose.yml -f docker-compose.override-nodory.yml up web
it seems to go
but if you open http://localhost:3000/
you have a page that says:
Routing Error
Not Found
Rails.root: /app/samvera/hyrax-webapp

Can some kind soul help me?

[bill bolt]

I'm getting the same error and this is years later

[Floyd, Randall Dean]

Greetings, I'm the new Hyrax Technical Lead for 2025.  I wanted to make sure you got a response even if I don't have an answer immediately at hand.

We aren't Hyku users here at Indiana University, but I did just try to build it and bring it up to see what my experience was.  I also received the error:

Permission denied @ rb_sysopen'   ./db/schema.rb

At that point it had just finished with database migrations and was trying to dump the DB to update the schema and couldn't because the user didn't have permissions to write to the file. Obviously there's something that needs to be tweaked in the Dockerfile to make sure the application user can write to that file at that point in time.  But, in this case, it actually started for me just by issuing the up command again immediately after the failure.  I guess it knew that DB migrations finished in the previous attempt and didn't need to pick back up in the initialization step, so it was still able to bring up the web container and the rest of the stack.

The message you referred to from 2023 didn't include the name of the file that it was unable to access, so I can't tell if what I experienced is relevant to your problem.  If it is the same, I think just a bit of troubleshooting the order of granting ownership/permissions to files during the build in the Dockerfile will fix it.

---

From: samver...@googlegroups.com <samver...@googlegroups.com> on behalf of bill bolt <lorddo...@gmail.com>
Sent: Monday, February 3, 2025 2:19 PM
To: samvera-tech <samver...@googlegroups.com>
Subject: [External] [samvera-tech] Re: troubles installing Hyku

 

This message was sent from a non-IU address. Please exercise caution when clicking links or opening attachments from external sources.

--
Samvera email lists are subject to the Samvera Code of Conduct and Anti-Harassment Policy
https://samvera.atlassian.net/wiki/spaces/samvera/pages/405212316/Samvera+Code+of+Conduct+and+Anti-Harassment+Policy
---
You received this message because you are subscribed to the Google Groups "samvera-tech" group.
To unsubscribe from this group and stop receiving emails from it, send an email to samvera-tech...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/samvera-tech/a012dde5-266f-4dc5-8833-1c2ffc94a581n%40googlegroups.com.

[Rob Kaufman]

Randall, Bill, 

I’m curious, what OS are you using? How do you have Docker (or containerd) installed? In 2023 the issue had to do with specific aspects of the Docker configuration. I’m very curious to leg down this issue. On my Mac, using Docker Desktop, Rancher Desktop or Colima, I do not see this particular error. I’d be happy to debug, especially if we can set it up so that I can reproduce the issue.

Best,

Rob

To view this discussion visit https://groups.google.com/d/msgid/samvera-tech/BN8PR08MB63558D9C7DA50BAD479F14F1D2F42%40BN8PR08MB6355.namprd08.prod.outlook.com.

[Floyd, Randall Dean]

Rob,

My setup is pretty straightforward.  It's Fedora Linux 41 running Docker Container Engine installed as a system package from the docker-ce-stable repository.  I did the bare minimum from the command line:

git clone https://github.com/samvera/hyku.git

docker compose build

docker compose up

That got me pretty far without incident, just the file write error to db/schema.rb.  When I issued 'up' again it all came up without forcing back into the initialize step.  But, when I shell into the web container, I can see that everything is still owned by 1000:1000 instead of the app user (1001).  Interestingly, the app user does own ./node_modules and ./tmp/cache, so it somehow wrote those directories.

---

From: samver...@googlegroups.com <samver...@googlegroups.com> on behalf of Rob Kaufman <r...@notch8.com>
Sent: Wednesday, February 5, 2025 9:40 PM
To: samver...@googlegroups.com <samver...@googlegroups.com>
Subject: [External] Re: [samvera-tech] Re: troubles installing Hyku

 

To view this discussion visit https://groups.google.com/d/msgid/samvera-tech/82516847-edda-4b07-84bc-39eb4460c2d6%40app.fastmail.com.