Troubleshooting

Troubleshooting Dockreg

If you’re encountering issues with Dockreg, this guide covers common problems and their solutions. For issues not covered here, check our support page or contact us directly.

Login Failures

Issue: “Error response from daemon: Get https://myapp.registry.dockreg.com/v2/: unauthorized: authentication required”

This error occurs when Docker cannot authenticate with your registry.

Solutions:

1. Verify credentials: Ensure your username and password (or API key) are correct. If using an API key, generate a new one from your account settings.
2. Check registry URL: Confirm you’re using the correct registry endpoint, e.g., myapp.registry.dockreg.com. It should match the one provided in your dashboard.
3. Network connectivity: Test access to the registry URL with curl https://myapp.registry.dockreg.com/v2/. If it fails, check your firewall or VPN settings.
4. Docker login command: Run docker login myapp.registry.dockreg.com and enter credentials carefully. Avoid special characters in passwords if possible.

If the issue persists, revoke and regenerate your credentials.

Push Errors

Issue: “Error response from daemon: push: manifest blob unknown”

This typically happens during image pushes due to authentication or configuration problems.

Solutions:

1. Tag the image correctly: Use the full path: docker tag myapp:latest myapp.registry.dockreg.com/myorg/myapp:latest. Replace myorg with your organization name.
2. Ensure login: Always run docker login before pushing. Verify with docker logout and docker login again if needed.
3. Registry permissions: Confirm your account has push access to the registry. Check organization-level permissions in the dashboard.
4. Image size limits: For the Starter plan, ensure your image doesn’t exceed storage limits. Use docker images to check sizes and consider multi-stage builds to reduce size.
5. Retry push: Sometimes transient network issues cause this. Run docker push myapp.registry.dockreg.com/myorg/myapp:latest again.

Issue: “denied: requested access to the resource is denied”

Solutions:

1. Public vs. private: Ensure the repository exists and is private if required. Create it in the dashboard if missing.
2. Namespace: Use the correct namespace (e.g., /myorg/myapp). Namespaces are case-sensitive.

Storage Limits

Issue: “Error: storage quota exceeded”

You’ve hit your plan’s storage limit (e.g., 10GB for Starter, 50GB for Team).

Solutions:

1. Check usage: Log in to your dashboard at https://dockreg.com/dashboard and view storage under “Usage & Billing”.
2. Delete unused images: Use the dashboard to remove old tags or images. Alternatively, via CLI: docker rmi <image-id> locally, then delete remotely if needed.
3. Upgrade plan: For more storage, upgrade to Team ($8/month) or Enterprise. Visit pricing.
4. Extra storage: On Starter/Team, additional storage is $0.05/GB. It auto-charges, but monitor to avoid surprises.
5. Optimize images: Compress layers or use tools like docker-squash to reduce image size before pushing.

General Tips

• Logs and monitoring: Enable real-time monitoring in your dashboard to track pushes/pulls and spot issues early.
• Vulnerability scanning (Beta): If scans fail, ensure images are pushed successfully first.
• Support: For 24/7 help, use our support channels. Enterprise users get phone support.

If these don’t resolve your issue, provide error logs when contacting support for faster resolution.