Harbor Troubleshooting Scenarios

Packages advent2025 ai ansible apache aws cli bash c caddy clickhouse cron csv data processing disk volumes dns docker elk envoy etcd financial finops ftp git gitea golang gunicorn hack haproxy harbor hashicorp vault helm java jenkins json kubernetes linux-other mongodb mysql nginx node.js php podman postgres prometheus python rabbitmq redis sql sqlite ssh ssl supervisord systemd terraform traefik

realistic / interviews new pro business

Harbor

Harbor registry scenarios

#	Name	Level	Time	Type
1	"Cabedelo": Harbor full of issues	Hard	40 m	Fix Pro	"Cabedelo": Harbor full of issues Scenario: "Cabedelo": Harbor full of issues Level: Hard Type: Fix Access: Paid Description: You need to build and push a docker image without changing the Dockerfile to your company's Harbor registry, which is running at harbor.sadservers.local, with its home directory at /opt/harbor. You have full admin access with admin:Harbor12345 credential. The source code and the Dockerfile are in the ~/app directory. The image name must be harbor.sadservers.local/images/app:1.0.0. It is also expected that the application will be up and running at localhost:5000 in a container named app. IMPORTANT. Do not: 1. Generate new internal certificates 2. Change the Dockerfile 3. Change the /opt/harbor.yml file Test: You are able to pull the application image from Harbor: `docker rmi harbor.sadservers.local/images/app:1.0.0` `docker pull harbor.sadservers.local/images/app:1.0.0` You can access the application; `curl localhost:5000` returns `Hello world!` The "Check My Solution" button runs the script /home/admin/agent/check.sh, which you can see and execute. Time to Solve: 40 minutes.

Harbor Troubleshooting Scenarios

Harbor

Harbor registry scenarios

"Cabedelo": Harbor full of issues

Send Us Feedback or Get Notified