[docker/cli] Suggestion: Docker images should have a "manifest" detailing the configuration options required to run a container

### ROOT CAUSE The primary issue stems from the absence of a standardized, accessible mechanism within Docker images to document the required configurations. This lack of information hinders tools and users from easily understanding and setting up containers without referring to external documentation. ### CODE FIX To address this issue, we propose introducing a standardized JSON manifest within Docker images. This manifest, placed in a designated location, will detail all necessary configuration options, such as ports, environment variables, and volume mounts. Here's how the implementation can proceed: 1. **Manifest Structure**: Define a JSON schema for the manifest, including details like ports, environment variables, and volume mounts. 2. **Dockerfile Modification**: Update the Dockerfile to include instructions for generating or including the manifest. This could involve using a new `dockerfile` instruction or a multi-stage build. 3. **Docker CLI Integration**: Modify Docker CLI to recognize and parse the manifest during container runtime, applying configurations automatically or prompting users as needed. 4. **Backward Compatibility**: Ensure existing images without a manifest continue to function as before, with tools gracefully handling their absence. 5. **Documentation Update**: Provide updated documentation to guide users on creating and using the manifest. ### Example Manifest

json
{
  "version": "1.0.0",
  "ports": [
    {
      "containerPort": 80,
      "protocol": "TCP",
      "description": "HTTP server"
    }
  ],
  "environmentVariables": [
    {
      "name": "DB_HOST",
      "required": true,
      "example": "localhost"
    }
  ],
  "volumes": [
    {
      "mountPath": "/var/www/html",
      "description": "Web application files"
    }
  ]
}


### Implementation Steps

1. **Define the Manifest Schema**: Establish a JSON schema for the manifest, ensuring all necessary configuration details are included.

2. **Update Dockerfile**: Introduce directives in Dockerfile to generate or include the manifest. For example, a new `MANIFEST` instruction or a multi-stage build step.

3. **Modify Docker CLI**: Enhance Docker CLI to parse the manifest during container creation, applying configurations and prompting users for missing information.

4. **Test and Validate**: Conduct thorough testing to ensure compatibility and functionality, both with and without the manifest.

5. **Educate Users**: Update documentation to explain the new manifest format and its benefits, encouraging its adoption within the Docker community.

This solution aims to enhance the usability of Docker containers by providing a structured, accessible configuration guide, making it easier for tools and users to interact with containers effectively.