Docker - in CI/CD
Which of the following GitHub Actions workflow step sequences correctly builds a Docker image named 'myapp' and pushes it to Docker Hub?
Which of the following GitHub Actions workflow step sequences correctly builds a Docker image named 'myapp' and pushes it to Docker Hub?
hard📝 Workflow Q8 of 15
Step-by-Step Solution
Solution:
Step 1: Login before pushing
You must authenticate to Docker Hub before pushing images. 1) docker build -t myapp . 2) echo ${{ secrets.DOCKER_PASSWORD }} | docker login -u ${{ secrets.DOCKER_USERNAME }} --password-stdin 3) docker push myapp logs in before pushing using the recommended '--password-stdin' method.Step 2: Build before push
The image must be built before pushing. 1) docker build -t myapp . 2) echo ${{ secrets.DOCKER_PASSWORD }} | docker login -u ${{ secrets.DOCKER_USERNAME }} --password-stdin 3) docker push myapp builds first, then logs in, then pushes.Step 3: Analyze other options
1) docker push myapp 2) docker build -t myapp . 3) docker login -u ${{ secrets.DOCKER_USERNAME }} -p ${{ secrets.DOCKER_PASSWORD }} pushes before building and logs in last, which is incorrect. 1) docker login -u ${{ secrets.DOCKER_USERNAME }} -p ${{ secrets.DOCKER_PASSWORD }} 2) docker build -t myapp . 3) docker push myapp uses '-p' flag which is deprecated and insecure. 1) docker build myapp . 2) docker push myapp 3) docker login -u ${{ secrets.DOCKER_USERNAME }} --password ${{ secrets.DOCKER_PASSWORD }} uses incorrect 'docker build myapp .' syntax and logs in after push.Final Answer:
Option A -> Option AQuick Check:
Build -> Login -> Push with correct syntax [OK]
Quick Trick: Login before pushing; build image first [OK]
Common Mistakes:
- Pushing before building the image
- Logging in after pushing
- Using insecure login flags like '-p' instead of '--password-stdin'
Master "in CI/CD" in Docker
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Docker Quizzes