nice to include the addon builder, better clear documentation about sensible defaults for environment variables.

[kundeng]

Looking for a one-line solution to spawn a dev environment, this project is very close.

Nice if you could also include the addon builder, some sample app templates, and improve sensible defaults.

I ran SPLUNK_EVENTGEN=1 SPLUNK_START_ARGS=--accept-license SPLUNK_ML=1 bash <(curl -Ls https://bit.ly/splunklab)
on mac on orbstack. port 8000 doesn't seem to work on localhost but fortunately splunklab.orbstack.local:8000 works, although the orbstack's secure, signed cert doesn't seem to be used.

Then I found out the container is removed, when I stop it! (missing another env variable).

[dmuth]

Answering these out of order:

Then I found out the container is removed, when I stop it!

As a general rule, Docker containers should be considered ephemeral. That is, the container itself is not long-lived, nor should it be expected to be long-lived. If there is something in the container that you want to persist outside of the container, it should be in a volume.

Nice if you could also include the addon builder, some sample app templates,

The what and the what? Please tell me where I can get these things. Or submit a PR if you prefer and we can go from there.

improve sensible defaults.

....? This does not give me anything useful to work with. What defaults are you running into issues with? I can't address things I don't know about.

Also, since Docker images can extend other images, depending on what you're looking to do, the quickest path forward may be to build your own container based on this one, with whatever defaults you'd like to see set up in the Dockerfile.

-- Doug