fix-redis

Identify and stop processes or containers occupying Redis port 6379.

3|1|Updated Jun 20, 2016
One-click install
npx skills add https://github.com/paulchiu/dotfiles --skill fix-redis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-redis
Source: https://github.com/paulchiu/dotfiles/tree/main/.config/opencode/skills/fix-redis
Command: npx skills add https://github.com/paulchiu/dotfiles --skill fix-redis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Redis port conflicts on 6379 during Docker/OrbStack container startup occur when another process or container holds the port. This skill identifies the conflicting holder and stops it so the new Redis container can start.

Core Features & Use Cases

  • Identify what is bound to port 6379
  • Find the Docker container publishing port 6379
  • Stop the offending owner (Docker container or host process)
  • Confirm the port is free and retry
  • Note: If multiple Redis containers from different projects conflict, suggest mapping one to a non-default host port (e.g. 6380:6379)

Quick Start

Identify the conflicting holder and stop it, then retry starting your Redis container.

Frequently Asked Questions about fix-redis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Redis Docker container fail to start with a port conflict on 6379?

A Redis container fails to start on port 6379 when another host process or Docker container is already bound to that port. This skill identifies the conflicting process or container and stops it to resolve the startup failure.

How do I find what process or container is using port 6379 in Docker or OrbStack?

To find what is using port 6379 in Docker or OrbStack, this skill checks port management mappings and running containers to identify the specific host process or container publishing the conflicting port.

What is the best way to resolve Redis port conflicts in an OrbStack development environment?

The best way to resolve Redis port conflicts in OrbStack is to locate the offending container or process holding port 6379, stop it, and then retry starting the new Redis container.

Can I run multiple Redis containers from different projects without changing the default 6379 port?

Running multiple Redis containers from different projects on the default 6379 port causes conflicts. This skill suggests mapping one container to a non-default host port, such as 6380:6379, to avoid startup failures.

How do I stop a Docker container that is occupying port 6379?

To stop a Docker container occupying port 6379, this skill identifies the specific container via port management checks, stops the offending container, confirms the port is free, and retries the Redis startup.