Closed pelesh closed 12 months ago
Unforunately we will need more of the error output to really know what's going on here, and how to fix it.
Key is that we need to see what the concrete spec actually was, and then we can figure out a way to avoid this buggy dependency. We have also merged quite a few things into develop. I am rebuilding myself now, and am also going to ensure the viz frontend is built already into the container.
This will also greatly simplify example notebook, so I will clean that up as well.
@pelesh I was able to reproduce on my machine, and this issue seems to have originated from https://github.com/spack/spack/pull/41083
A temporary fix is I am now building with libffi@3.4.2
, but I think this warrants a spack issue / comment on that PR.
I didn't look too hard to see if Spack PR already exists, but this change is 5 days old, so I think we happened to catch an edge case here...
This does motivate pinning of a spack version within the container that we are building, and would perhaps need some help from @rothpc and techniques discussed offline in order to maintain exago's package alongside the pinned version of Spack that won't be getting regular updates.
Then again it is nice to keep up to date with spack develop, and I think #52 and CI/CD to cache a build of this devconatiner will help a lot.
Unfortunately this build would not be with Ipopt until we can build ipopt+resolve
.
Issue type
Relates to
Summary
Generating docker image following ExaGO instructions fails.
Exact commands to reproduce, if applicable
On MacOS arch follow instructions to the letter.
Relevant logs and/or screenshots, if applicable
Possible fixes, if applicable
No obvious fixes.