[I] [Docs] Make Quickstart container startup checks explicit [fluss]

["wuchong (via GitHub)" <gi...@apache.org>]

wuchong opened a new issue, #4433:
URL: https://github.com/apache/fluss/issues/4433

   ### Problem
   
   Several Quickstart guides ask users to inspect `docker compose ps` after starting the environment. This makes it easy to overlook a failed or missing container, especially in stacks that also contain expected one-shot or interactive services.
   
   ### Proposed change
   
   - Count the expected long-running containers after `docker compose up -d`.
   - Document the expected count for each Quickstart stack.
   - Exclude services such as `rustfs-init` and `sql-client` that may exit normally.
   - Direct users to `docker compose ps -a` when the count is lower than expected.
   
   The same documentation improvement should be applied to `main` and backported to `release-1.0`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] [Docs] Make Quickstart container startup checks explicit [fluss]

["wuchong (via GitHub)" <gi...@apache.org>]

wuchong closed issue #4433: [Docs] Make Quickstart container startup checks explicit
URL: https://github.com/apache/fluss/issues/4433


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org