homelab-optimized/docs/services/individual/piped-proxy.md

Piped Proxy

🟢 Other Service

📋 Service Overview

Property	Value
Service Name	piped-proxy
Host	concord_nuc
Category	Other
Difficulty	🟢
Docker Image	1337kavin/piped-proxy:latest
Compose File	concord_nuc/piped.yaml
Directory	concord_nuc

🎯 Purpose

piped-proxy is a specialized service that provides specific functionality for the homelab infrastructure.

🚀 Quick Start

Prerequisites

• Docker and Docker Compose installed
• Basic understanding of REDACTED_APP_PASSWORD
• Access to the host system (concord_nuc)

Deployment

# Navigate to service directory
cd concord_nuc

# Start the service
docker-compose up -d

# Check service status
docker-compose ps

# View logs
docker-compose logs -f piped-proxy

🔧 Configuration

Docker Compose Configuration

container_name: piped-proxy
environment:
- UDS=1
image: 1337kavin/piped-proxy:latest
restart: unless-stopped
volumes:
- piped-proxy:/app/socket

Environment Variables

Variable	Value	Description
UDS	1	Configuration variable

Port Mappings

No ports exposed.

Volume Mappings

Host Path	Container Path	Type	Purpose
piped-proxy	/app/socket	volume	Data storage

🌐 Access Information

This service does not expose any web interfaces.

🔒 Security Considerations

• ⚠️ Consider adding security options (no-new-privileges)
• ⚠️ Consider running as non-root user

📊 Resource Requirements

No resource limits configured

Recommended Resources

• Minimum RAM: 512MB
• Recommended RAM: 1GB+
• CPU: 1 core minimum
• Storage: Varies by usage

Resource Monitoring

Monitor resource usage with:

docker stats

🔍 Health Monitoring

⚠️ No health check configured Consider adding a health check:

healthcheck:
  test: ["CMD", "curl", "-f", "http://localhost:PORT/health"]
  interval: 30s
  timeout: 10s
  retries: 3

Manual Health Checks

# Check container health
docker inspect --format='{{.State.Health.Status}}' CONTAINER_NAME

# View health check logs
docker inspect --format='{{range .State.Health.Log}}{{.Output}}{{end}}' CONTAINER_NAME

🚨 Troubleshooting

Common Issues

Service won't start

• Check Docker logs: docker-compose logs service-name
• Verify port availability: netstat -tulpn | grep PORT
• Check file permissions on mounted volumes

Can't access web interface

• Verify service is running: docker-compose ps
• Check firewall settings
• Confirm correct port mapping

Performance issues

• Monitor resource usage: docker stats
• Check available disk space: df -h
• Review service logs for errors

Useful Commands

# Check service status
docker-compose ps

# View real-time logs
docker-compose logs -f piped-proxy

# Restart service
docker-compose restart piped-proxy

# Update service
docker-compose pull piped-proxy
docker-compose up -d piped-proxy

# Access service shell
docker-compose exec piped-proxy /bin/bash
# or
docker-compose exec piped-proxy /bin/sh

📚 Additional Resources

• Official Documentation: Check the official docs for piped-proxy
• Docker Hub: 1337kavin/piped-proxy:latest
• Community Forums: Search for community discussions and solutions
• GitHub Issues: Check the project's GitHub for known issues

🔗 Related Services

Other services in the other category on concord_nuc

---

This documentation is auto-generated from the Docker Compose configuration. For the most up-to-date information, refer to the official documentation and the actual compose file.

Last Updated: 2025-11-17
Configuration Source: concord_nuc/piped.yaml