REGEXVAULT
Dev & Systems/Docker
ReDoS Checked

Docker Port Mapping Regex for Go

/^(?:(?:(?:(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9]):)?(?:6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{0,3}):)?(?:6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{0,3})(?:/(tcp|udp|sctp))?$/i

All five implementations are free. Switch engines without signing in.

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching docker port mapping, ported and verified for Go. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your Go project — whether you're validating in a Gin handler, a gRPC service, or a command-line tool.

Go Implementation

Go
// Docker Port Mapping
// ReDoS-checked | RegexVault — Dev & Systems > Docker

package validation

import "regexp"

var dockerPortMappingRe = regexp.MustCompile(`^(?:(?:(?:(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9])\.){3}(?:25[0-5]|2[0-4][0-9]|1[0-9]{2}|[1-9][0-9]|[0-9]):)?(?:6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{0,3}):)?(?:6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|6[0-4][0-9]{3}|[1-5][0-9]{4}|[1-9][0-9]{0,3})(?:/(tcp|udp|sctp))?$`)

func ValidateDockerPortMapping(s string) bool {
    return dockerPortMappingRe.MatchString(s)
}

// Example
// fmt.Println(ValidateDockerPortMapping("8080:80")) // true

Test Cases

Matches (Valid)
Rejects (Invalid)
8080:800:80
127.0.0.1:8080:808080:0
0.0.0.0:443:44399999:80
808080:99999
8080:80/tcphost:80:80
3000:3000/udp8080:80/http

When to use this pattern

This pattern is drawn from the Dev & Systems > Docker category and has been checked for ReDoS risk. That matters for Go developers because Go's RE2 engine is inherently safe from catastrophic backtracking, but this pattern has been additionally verified for correctness. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

Publishing 0.0.0.0:port exposes services on all interfaces including public ones. Always bind to 127.0.0.1 for development services unless public access is intentional.

Technical Notes

Protocol defaults to tcp. Exposing on 0.0.0.0 (all interfaces) is the default. Use 127.0.0.1 to restrict to localhost for development services.

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Submissions join the review queue after automated validation.

Submit a Pattern