InfluxDB 2.x OSS fresh-start bucket provisioning limits

When standing up a repeatable development environment with InfluxDB 2.x OSS, the initialization behavior on an empty data directory determines whether automated provisioning is strictly required. The goal is to ensure every fresh container instance reaches a writable state without manual intervention.

InfluxDB 2.x OSS is documented to require an organization and bucket before the write API accepts data, and it does not create them automatically when started with an empty data directory. This creates an unresolved design question for teams migrating from InfluxDB 1.x workflows that assumed a default database, or for teams building container startup automation that must account for this explicit setup phase.

What is the documented boundary between automatic and manual provisioning during InfluxDB 2.x OSS initialization? Does the CLI or API expose any supported mechanism to seed an initial organization and bucket during first startup, or must external tooling handle this before writes are attempted? How should automation detect and handle the absence of these resources to avoid silent write failures?