AI Prompts for Prevent Unexpected Dockerfile Modifications

Please provide the last output generated when modifying the Dockerfile. Identify the specific line that was changed and explain how it aligns or does not align with the original Dockerfile requirements. Additionally, summarize any potential impacts this change may have on the overall functionality of the Docker configuration.

Please analyze the following Dockerfile content for discrepancies or unexpected modifications: [DOCKERFILE CONTENT]. Identify any potential issues that could affect the build process or runtime performance. Provide a detailed report highlighting the problems found, along with suggestions for corrections and best practices to follow.

Please summarize your interpretation of my last instruction regarding the Dockerfile modifications. Include any key points or potential areas of misunderstanding that may need clarification before you proceed with the changes. This summary should be concise yet comprehensive enough to ensure we are aligned on the next steps.

Please provide a detailed comparison between the expected Dockerfile configuration and the actual changes made. Highlight the specific sections where modifications occurred, clearly indicating what was intended versus what was modified unexpectedly. Include a summary of potential impacts these changes may have on the overall functionality and performance of the Docker container.

Identify the specific rule or constraint that was violated during the last modification of the Dockerfile. Please quote the exact wording of the rule and provide a brief explanation of how it was not adhered to in the modification process. Additionally, suggest potential steps to rectify the violation and prevent it from occurring in future modifications.

Revert the line at Dockerfile:12 to its original state, which is 'FROM node:14'. Ensure that no other parts of the Dockerfile are modified in this process. After making the change, provide a brief summary of the modifications made and confirm that the Dockerfile is still functional.

Rewrite the CI configuration to ensure it adheres to the following constraints: use Node.js version 14 and ensure all dependencies are installed before the build step. Provide a detailed explanation of how each constraint is enforced within the configuration file. Additionally, include comments in the code to clarify the purpose of each section and any potential pitfalls to avoid during implementation.

Please modify the Dockerfile by changing the line at line 15 that specifies the working directory. Set it back to 'WORKDIR /app' while ensuring that no other lines in the Dockerfile are altered. After making this change, provide a brief summary of the impact this adjustment may have on the build process and application execution.

Please review the following Dockerfile: [DOCKERFILE CONTENT]. Ensure that it adheres to the correct format for each instruction. Specifically, check that all commands are in uppercase, properly spaced, and follow best practices for Dockerfile syntax. Provide a detailed report on any formatting issues found and suggest corrections for each identified problem.

Review the CI configuration for the project related to [PROJECT NAME]. Identify any missing dependencies that could cause issues during the build process. Specifically, ensure that the command 'npm install' is included before the build step to prevent runtime errors. Provide a detailed report on any changes needed, including the specific lines of code to modify and the rationale for each change.

Please execute a Docker build command using the Dockerfile located at [DOCKERFILE_PATH]. Verify that the build completes successfully without any errors in the output. After the build process, provide a summary of the build results, including any warnings or messages that may have appeared during the process.

Please display the diff of the Dockerfile before and after the changes were made. Ensure that the output highlights only the lines that were modified, added, or removed, and provide a clear summary of the changes. This will help confirm that only the intended modifications were applied and allow for easy review of the differences.

Replay the last CI task that failed due to modifications in the Dockerfile. Analyze the output logs to identify any errors that occurred during the previous run. Confirm whether the task now completes successfully without any errors, and provide a summary of the changes made to the Dockerfile that resolved the issues.

Please verify the CI configuration by testing it with an edge case scenario where a dependency is missing. Document how the CI handles this situation, ensuring that there are no unexpected modifications to the configuration or environment. Provide a detailed report that includes the steps taken during the test, the behavior observed, and any recommendations for improving error handling in the CI process.

Please analyze the current state of the Dockerfile located at [DOCKERFILE_PATH] and confirm whether it matches the expected configuration outlined in [EXPECTED_CONFIGURATION]. If there are any discrepancies, provide a detailed report highlighting the differences and suggest necessary adjustments to align it with the expected state.

Please create a session-opening constraint for the project related to Dockerfile modifications. The constraint should specify: 'Before any Dockerfile modification, verify that no unintended changes are made to lines 10-20. If any changes occur, stop and revert to the last stable version before continuing.' Ensure the wording is clear and concise for team members to follow.

Generate a conversation-starter template for a CI configuration integrity check. The template should include a checklist that prompts users to confirm that the CI configuration aligns with the expected template before executing any CI tasks. If any deviations are detected, the template should instruct to halt the process and document the changes. Ensure the output is structured as a clear checklist with sections for confirmation, deviation reporting, and action steps.

Please create a detailed guideline for establishing a naming convention for Dockerfiles. The guideline should specify that all Dockerfiles must be named in the format: 'Dockerfile.[SERVICE_NAME]'. Include the importance of adhering to this convention, potential issues that may arise from non-compliance, and examples of correctly named Dockerfiles. Additionally, suggest ways to enforce this naming convention within a team or organization.

Create a self-check request for a CI agent that runs before any CI task is executed. The request should verify that all dependencies listed in [PACKAGE.JSON PATH] are installed. If any dependencies are missing, the agent should immediately alert the user with a clear message indicating which dependencies need to be installed.

Please implement a requirement for documenting changes in the Dockerfile by creating a CHANGELOG.md file. Ensure that every modification to the Dockerfile is recorded with the following details: the date of the change, the author's name, and a brief description of the change made. Format the CHANGELOG.md file with clear headings for each entry to enhance readability and maintainability.