Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LSIO_FIRST_PARTY in container branding docs #312

Merged
merged 2 commits into from
Mar 15, 2025
Merged

LSIO_FIRST_PARTY in container branding docs #312

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5c85187
LSIO_FIRST_PARTY in container branding docs
jmbannon Mar 15, 2025
38763f3
Update container-branding.md
jmbannon Mar 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/general/container-branding.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,4 +16,8 @@ On start-up, the base image will automatically load the branding into its init,

Hopefully this makes it simpler for everyone to manage the branding of your images when using our bases.

!!! note

If you're branding a non-base image, you must set the ENV variable `LSIO_FIRST_PARTY=false` to avoid LSIO from overwriting it.

A final note: if you've previously overridden the `init-adduser` run file to do custom branding, we recommend switching to the above approach so that you don't miss out on any future changes to that init step.