Just saw this announcement and wanted to share with the community. Docker Desktop alternative gains traction - Podman Desktop 2.0
This could have significant implications for teams using Terraform. What does everyone think about this development?
Key points:
- Better security
- Migration guide available
- Limited beta access
Anyone planning to adopt this soon?
For those asking about cost: in our case (AWS, us-east-1, ~500 req/sec), we're paying about $5000/month. That's 70% vs our old setup with Docker. ROI was positive after just 2 months when you factor in engineering time saved.
Here's our production setup:
- Tool A for X
- Tool B for Y
- Custom scripts for Z
Happy to share more details if interested.
This aligns with our experience. Highly recommend this approach.
Be careful with this approach. We had production issues.
We evaluated Grafana last quarter and decided against it due to migration complexity. Instead, we went with ArgoCD which better fit our use case. The main factors were cost (30% cheaper), ease of use (2-day vs 2-week training), and community support.
We evaluated GitHub Actions last quarter and decided against it due to migration complexity. Instead, we went with Terraform which better fit our use case. The main factors were cost (30% cheaper), ease of use (2-day vs 2-week training), and community support.
The migration path we took:
Week 1-2: Research & POC
Week 3-4: Staging deployment
Week 5-6: Prod rollout (10% -> 50% -> 100%)
Week 7-8: Optimization
Total cost: ~200 eng hours
Would do it again in a heartbeat.
We tried this but hit issues with X. How did you solve it? Trying to build a business case for management.
Did you use version X or Y? We found Y more stable. Our team is particularly concerned about production stability.
How does this scale? We're running 100+ services. Trying to build a business case for management.
Thanks for sharing! We're planning to try this next quarter.
Pro tip: if you're implementing this, make sure to configure timeout settings correctly. We spent 2 weeks debugging random failures only to discover the default timeout was too low. Changed from 30s to 2min and all issues disappeared.
We implemented this using the following approach:
1. First step...
2. Then we...
3. Finally...
Results: significant improvement in deployment speed. Timeline: 4 weeks from POC to production.
Cautionary tale: we rushed this implementation without proper testing and it caused a 4-hour outage. The issue was memory leak in the worker. Lesson learned: always test in staging first, especially when dealing with authentication services.