We did not -- just set up a true local dev env instead.

On Wednesday, June 21, 2023 at 1:27:34 PM UTC-4 [email protected] wrote:

> Hi Stephen, 
>
> Did you ever get this working? I am running into this on my M1 Mac.
>
> Thanks!
> Tom
>
> On Wednesday, January 26, 2022 at 12:33:23 PM UTC-6 Stephen Brush wrote:
>
>>  I never resolved the Docker issue. It could have been related to overall 
>> memory usage on my PC but nothing to me suggested it was a problem.
>>
>> I ended up setting up a local Dev env on my Windows machine since that 
>> would be required anyways in the future. The docs I had to reference were 
>> pretty old -- I captured some notes here in case anyone is up for updating 
>> the docs on Confluence.
>>
>>
>>
>> On Thursday, January 20, 2022 at 3:22:28 PM UTC-5 Tim Donohue wrote:
>>
>>> Hi Steve,
>>>
>>> I can verify that these Docker scripts work on my end (I use Docker 
>>> almost daily to test new features/code being built for DSpace 7).  The 
>>> "Javascript heap out of memory." error almost sounds like your Docker 
>>> installation ran out of memory on your local machine.  Could you describe a 
>>> bit more about your setup?  For instance, what OS are you using?  Do you 
>>> have sufficient memory on your machine (to run all the Docker images 
>>> together, you honestly may need 4-6GB at least just for Docker)?  Are you 
>>> installing Docker Desktop (like noted at 
>>> https://wiki.lyrasis.org/display/DSPACE/Try+out+DSpace+7#TryoutDSpace7-InstallviaDocker),
>>>  
>>> or are you using some different version of Docker?
>>>
>>> While we honestly haven't tested these Docker scripts on every single 
>>> OS, I've been told they work on Mac, and I'm on Windows 10 myself.   It's 
>>> possible there's some new bug or issue that has come up recently, but I can 
>>> verify that I have these Docker scripts running on Windows 10 today.
>>>
>>> I should also note, if you are just trying to try out the UI, it's also 
>>> possible to just install the UI quickly on its own & use our public demo 
>>> REST API as the backend. That doesn't even require Docker.  Here's that 
>>> setup: 
>>> https://wiki.lyrasis.org/display/DSPACE/Try+out+DSpace+7#TryoutDSpace7-InstalltheUserInterfaceonly
>>>
>>> If you can send us more basic info on this list about your setup, it's 
>>> possible we'd be able to figure out what is causing the Docker scripts not 
>>> to work for you.
>>>
>>> Tim
>>>
>>> On Monday, January 17, 2022 at 12:51:33 PM UTC-6 [email protected] 
>>> wrote:
>>>
>>>> UPDATE -- still not working.
>>>>
>>>> I tried the instructions from another link 
>>>> <https://wiki.lyrasis.org/display/DSPACE/Try+out+DSpace+7>, though 
>>>> they are basically the same and had the same results. I can reach the HAL 
>>>> browser on the REST server, but the Angular front end fails with
>>>>
>>>> FATAL ERROR: Ineffective mark-compacts near heap limit Allocation 
>>>> failed - Javascript heap out of memory.
>>>>
>>>> Is this happening for anyone else??
>>>>
>>>> [image: angular-error2.png]
>>>>
>>>> Steve
>>>> On Wednesday, January 12, 2022 at 2:07:48 PM UTC-5 Stephen Brush wrote:
>>>>
>>>>>
>>>>> 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/ba380c30-a58a-45f3-aa2e-2dab29baafd0n%40googlegroups.com.

Reply via email to