I believe I am using the standard instructions from the README file from https://github.com/DSpace/DSpace/tree/dspace-7.1/dspace/src/main/docker-compose .
>From the instructions: docker-compose -f docker-compose.yml -f docker-compose-cli.yml pull docker-compose -p d7 -f docker-compose.yml -f dspace/src/main/docker-compose/docker-compose-angular.yml up -d This results in dspace-angular image ID '458d242c63ba' being pulled and run, with that fatal error happening in the logs. I don't think what I have on my host is any consequence as the node/yarn actions are taking place in the container correct? It appears the image has node v14.18.2 and yarn 1.22.15 installed. I guess the dspace-angular project is separate on GitHub -- but I assume that should not matter as the above commands just leverage the image that project creates. Steve On Tuesday, January 11, 2022 at 5:30:47 PM UTC-5 Tim Donohue wrote: > Hi, > > Yes, the dspace-angular Docker image based on `main` codebase is still > working. It's sample Docker compose files can be found at > https://github.com/DSpace/dspace-angular/tree/main/docker > > It's possible you are using an old or outdated (or third party) Docker > image, as you didn't specify which one you are using, or what instructions > you may be following. > > That specific error seems to imply you are using a incorrect version of > Node. The DSpace Angular UI requires Node 12 or 14, and as that > StackOverflow question you linked to says, one of the "answers" was to > upgrade to Node v12. > > In any case, I can verify that the Docker images based on the GitHub > codebase are maintained & updated every time we push out a code change. > However, we don't recommend running them in Production at this time, as > they have not be tested in Production scenarios. They are also available > at https://hub.docker.com/r/dspace/dspace-angular > > If you have other questions, let us know on this list > > Tim > > On Tuesday, January 11, 2022 at 3:06:37 PM UTC-6 [email protected] wrote: > >> Is the Docker image for front end still active and working for others? >> >> I receive the following when starting that container: >> >> FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed >> - Javascript heap out of memory >> >> [image: angular-error.png] >> >> https://stackoverflow.com/questions/53230823/fatal-error-ineffective-mark-compacts-near-heap-limit-allocation-failed-javas >> > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/439fa364-dfbf-41e0-97c7-6b173d0107edn%40googlegroups.com.
