Forum

Search
Preferences
AI Search
Classic Search
 Search Phrase:
 Search Type:
Advanced search options
 Search in Forums:
 Search in date period:

 Sort Search Results by:

AI preferences coming soon...

AI Assistant
Docker Desktop alte...
 
Notifications
Clear all

Docker Desktop alternative gains traction - Podman Desktop 2.0

17 Posts
15 Users
0 Reactions
414 Views
(@samuel.miller567)
New Member
Joined: 5 months ago
Posts: 0
Topic starter  

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?



   
Quote
(@david.morales35)
New Member
Joined: 9 months ago
Posts: 0
 

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.



   
ReplyQuote
(@william.smith189)
New Member
Joined: 1 month ago
Posts: 0
 

Here's our production setup:
- Tool A for X
- Tool B for Y
- Custom scripts for Z
Happy to share more details if interested.



   
ReplyQuote
(@patricia.morgan347)
New Member
Joined: 3 months ago
Posts: 0
 

This aligns with our experience. Highly recommend this approach.



   
ReplyQuote
Paul
 Paul
(@paul)
New Member
Joined: 1 month ago
Posts: 0
 

Be careful with this approach. We had production issues.



   
ReplyQuote
(@sharon.garcia321)
New Member
Joined: 5 months ago
Posts: 0
 

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.



   
ReplyQuote
Sara Pike
(@sara)
New Member
Joined: 1 month ago
Posts: 0
 

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.



   
ReplyQuote
(@william.harris811)
New Member
Joined: 4 months ago
Posts: 0
 

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.



   
ReplyQuote
(@brandon.williams519)
New Member
Joined: 4 months ago
Posts: 1
 

We tried this but hit issues with X. How did you solve it? Trying to build a business case for management.



   
ReplyQuote
(@david.morales35)
New Member
Joined: 9 months ago
Posts: 0
 

Did you use version X or Y? We found Y more stable. Our team is particularly concerned about production stability.



   
ReplyQuote
(@alexander.rodriguez755)
New Member
Joined: 12 months ago
Posts: 0
 

How does this scale? We're running 100+ services. Trying to build a business case for management.



   
ReplyQuote
(@elizabeth.perez157)
New Member
Joined: 8 months ago
Posts: 0
 

Thanks for sharing! We're planning to try this next quarter.



   
ReplyQuote
(@karen.thomas72)
New Member
Joined: 9 months ago
Posts: 0
 

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.



   
ReplyQuote
(@emily.gutierrez57)
New Member
Joined: 5 months ago
Posts: 0
 

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.



   
ReplyQuote
Paul
 Paul
(@paul)
New Member
Joined: 1 month ago
Posts: 0
 

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.



   
ReplyQuote
Page 1 / 2
Share:
Scroll to Top