Fix startup errors in mlx-ui Docker container (prereg to run on OpenShift)

[jbusche]

With these 3 file tweaks, this currently is starting up successfully on an OpenShift 4.8 cluster.

• don't mv build/ proc/ use build folder directly for running the node application

Resolves #337

Related IBM/manifests#41

[Tomcli]

/lgtm

[Tomcli]

@yhwang this looks good to you?

[ckadner]

Thank you @jbusche -- did you find that the change group workaround was no longer needed?

RUN chgrp -R 0 /workspace && chmod -R g=u /workspace

[yhwang]

the change works on IKS. good job

[jbusche]

Hi @ckadner I'd forgotten about that, with the original instructions, when using:
git clone https://github.com/machine-learning-exchange/manifests -b mlx-single-user
I found this DID need the chgrp fix.

But when @Tomcli made some changes and had me use his latest from:
https://github.com/tomcli/manifests
Then the chgrp wasn't required anymore, but other errors cropped up, or perhaps we got further where they became apparent.

[ckadner]

Thank you @jbusche -- did you find that the change group workaround was no longer needed?

RUN chgrp -R 0 /workspace && chmod -R g=u /workspace

@Tomcli added a emptyDir build volume in the deployment manifest

        volumeMounts:
        - ...
          # When deploying MLX on OpenShift, readOnly SCC may be required for mlx-ui.
        - mountPath: /workspace/build
          name: build-volume
          # When deploying MLX on OpenShift, emptydir volume is required

      volumes:
      - ...
      - name: build-volume
        emptyDir: {}

See https://github.com/IBM/manifests/pull/41/files#diff-4c13edf3f1d7a1733c756e376d908ee0e268b5df78b525b271e536b781807dd1R66-R83

[ckadner]

/lgtm

[mlx-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ckadner, jbusche, yhwang

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ckadner,yhwang]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment