-
-
Notifications
You must be signed in to change notification settings - Fork 278
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.
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
OCI entrypoint configuration #1558
Comments
|
But yeah, I agree that having a proper way of handling the entry point command would be good as we don't really want folks messing with |
Another popular project which requires the raw.lxc command is Authentik. Depending on your setup you need multiple instances where you need to edit the raw.lxc to start the right process. Thanks for looking into it. |
@stgraber Could we just have a So in the case of keycloak it would be like I think there's no way to get completely docker-like behaviour due to the |
Yeah. I was thinking of introducing:
As config keys which we would preset to the value from config.json if not directly provided by the user (same behavior we have for environment.). |
Oh right, those others would be pretty neat too. I'll see about making a PR in the next days. |
Hello,
I'd like to install Keycloak as Incus OCI image.
Download worked fine, but I cannot get the container to start because a parameter needs to be passed (see: https://www.keycloak.org/getting-started/getting-started-docker)
However, I've tried passing it via
raw.lxc: lxc.execute.cmd="start-dev"
Also tried using
raw.lxc: lxc.execute.cmd="kc.sh start-dev"
Container still complains about not having the right or any argument for kc.sh and exits.
Is there any workaround for this?
Distribution of Host: Debian 12
Version: stable (as of 2025-01-05)
Kernel: 6.1.0-28-amd64 (Debian default)
Storage backend: lvm
Thank you!
The text was updated successfully, but these errors were encountered: