Commit 3cd3c34
authored
Add m365 CLI to aipcc-based image, build gog/m365 from our forks (#9)
* Add m365 CLI to aipcc-based CSB image
npm install --prefix on a plain git URL failed silently: the fork lacked
a "prepare" script, so npm never built dist/ before packing, leaving no
m365 binary to symlink. Fixed upstream in tssala23/cli-microsoft365 by
adding "prepare": "npm run build" (commit 6188d33), so the plain
`npm install <git-url>#<commit>` + symlink now works as expected.
Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com>
Signed-off-by: Pavel Anni <panni@redhat.com>
* Build gog and m365 from our forks instead of upstream releases
Both gogcli and cli-microsoft365 are forked (rh-forge) so we can ship
changes ahead of upstream merge. Add a multi-stage build for gog from
source (github.com/rh-forge/gogcli) instead of pulling an upstream
release tarball, and point the m365 npm install at our fork
(github.com/rh-forge/cli-microsoft365) instead of a coworker's fork.
Also reclaim /sandbox ownership after both CLI installs, since m365's
`m365 version` smoke test writes root-owned config under $HOME during
the build.
Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com>
Signed-off-by: Pavel Anni <panni@redhat.com>
* Address CodeRabbit findings: pin base image digests, fix OpenShift GID-0 perms
Pin both FROM images (golang builder, aipcc runtime base) to their current
manifest-index digests so rebuilds can't silently pick up different image
content. Also fix ownership/permissions on /sandbox for OpenShift's
restricted-v2 SCC, which runs the container as an arbitrary UID but always
keeps it in supplemental group 0: chown to <owner>:0 with chmod -R g=u
instead of a fixed sandbox:sandbox owner with owner-only 0700, matching the
pattern already used in Containerfile/Containerfile.hi/Containerfile.openclaw.
Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com>
Signed-off-by: Pavel Anni <panni@redhat.com>
* Document deferred CodeRabbit lockfile finding as inline TODO
CodeRabbit flagged that the m365 fork install has no lockfile, so
transitive npm deps can float between builds even at a pinned commit.
Valid, but out of scope while we're still building images manually for
testing (redhat-et/openclaw-csb has issues disabled, so track it inline
instead of in a tracker).
Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com>
Signed-off-by: Pavel Anni <panni@redhat.com>
---------
Signed-off-by: Pavel Anni <panni@redhat.com>1 parent dd9feb5 commit 3cd3c34
1 file changed
Lines changed: 79 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
| 41 | + | |
| 42 | + | |
| 43 | + | |
| 44 | + | |
| 45 | + | |
| 46 | + | |
| 47 | + | |
| 48 | + | |
| 49 | + | |
| 50 | + | |
| 51 | + | |
| 52 | + | |
| 53 | + | |
| 54 | + | |
| 55 | + | |
| 56 | + | |
| 57 | + | |
| 58 | + | |
| 59 | + | |
| 60 | + | |
| 61 | + | |
| 62 | + | |
| 63 | + | |
| 64 | + | |
| 65 | + | |
| 66 | + | |
| 67 | + | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
0 commit comments