How to create a workspace based on a minimal ansible creator-ee image

[l0rd]

Summary

I forked the repo https://github.com/kyetter/ansible-devspace-demo and then I modified the image property in the devfile.yaml to reference my EE minimal that I built and store in Quay:

https://github.com/ansiblejunky/ansible-devspaces-demo/blob/f9899e175e71664f81d084d810aad496bbfd6d53/devfile.yaml#L8C56-L8C56

And when I use this repo, I get these errors when trying to spin up the workspace:

Pworkspace843e055e9adb47db-856fbf68df-ggw4n
Generated from kubelet on ip-10-0-237-6.us-east-2.compute.internal
12:44:24
PostStartHook failed

Pworkspace843e055e9adb47db-856fbf68df-ggw4n
Generated from kubelet on ip-10-0-237-6.us-east-2.compute.internal
12:44:24
FailedPostStartHook

Pworkspace843e055e9adb47db-856fbf68df-ggw4n
Generated from kubelet on ip-10-0-237-6.us-east-2.compute.internal
12:44:24
MountVolume.SetUp failed for volume "che-gateway" : configmap "workspace843e055e9adb47db-route" not found

Pworkspace843e055e9adb47db-856fbf68df-ggw4n
Generated from kubelet on ip-10-0-237-6.us-east-2.compute.internal
12:44:23
Pulling image "quay.io/jwadleig/ansible-ee-minimal:latest"

Originally posted by @ansiblejunky in #21778 (comment)

[l0rd]

In the original Dev Spaces sample we use this Dockerfile to add a few things on top of latest quay.io/ansible/creator-ee.

In particular there are some mandatory configurations that you need to add to the creator-ee if you want to make it start successfully:

1. Set the $HOME folder (required by OpenShift):

ENV HOME=/home/runner

2. Install nodejs v16.20 (or VS Code will failed to run on the creator-ee image): (Note that this won't be necessary anymore when #21778 is resolved)

RUN \
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.3/install.sh | bash && \
export NVM_DIR="$HOME/.nvm" && \
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" && \
nvm install 16.20.0
ENV VSCODE_NODEJS_RUNTIME_DIR="$HOME/.nvm/versions/node/v16.20.0/bin/"

3. Set permissions on /etc/passwd and /home to allow arbitrary users to write (required by OpenShift):

RUN chgrp -R 0 /home && chmod -R g=u /etc/passwd /etc/group /home

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.