"Try out DSpace 9" Docker instructions no longer work. The UI never starts.

[tdonohue]

Describe the bug

The "Try out DSpace 9" Docker instructions no longer work properly. If you follow them step-by-step, then the backend starts up, but the UI does not.

To Reproduce

Steps to reproduce the behavior:

1. Follow the "Try out DSpace 9" Docker instructions
2. Verify that https://localhost:8080/server/ will respond after running those commands. However http://localhost:4000/ will not respond. It hangs indefinitely. The logs of the docker container are no help, as no errors appear.. the containers logs stop abruptly.
   • I've tried waiting for 30+ minutes in case the npm run serve command is just taking a while to build the UI. But, after that time there's still nothing new in the logs and the UI is still unresponsive.
   • Passing the --verbose flag to the npm run serve command also seems to provide no additional details in the logs of the dspace-angular container.

Expected behavior

Obviously, these instructions should work. It appears these docker images or the docker-compose scripts have been accidentally broken along the way.

[saschaszott]

@tdonohue, does the problem still occur if you include the changes from this commit 5215fac in package.json? This was already fixed in main branch by PR #4810.

[saschaszott]

BTW: we should better use the exec form in the CMD directive and rewrite

dspace-angular/Dockerfile

Line 26 in a54c4f8

CMD npm run serve -- --host 0.0.0.0

to

CMD ["npm", "run", "serve", "--", "--host", "0.0.0.0"]

[tdonohue]

@tdonohue, does the problem still occur if you include the changes from this commit 5215fac in package.json? This was already fixed in main branch by PR #4810.

@saschaszott : Yes, I'm already testing using latest main, which includes that commit. I also tried removing that change...but then I get an immediate error on startup of the UI. So, the change in that commit seems to be working, but it doesn't fix the issue in this ticket.

I also agree with your note about rewriting the CMD directives. I'll make sure that's in the final PR. I've tried it locally as well and doesn't have impact on this bug...but I agree it's the best practice.