dockware
  • dockware doc's
  • News
  • Setup
    • Docker Setup
    • What Image should you use?
    • Performance Tweaks
  • Use Dockware
    • First Run
    • Update Dockware
    • Advanced Run
    • Default Credentials
    • Symfony or Shopware 5
    • Changelog
  • Features
    • Intro
    • Environment Variables
    • Adminer
    • Mailcatcher
    • Switch PHP Version
    • Switch Node Version
    • Tideways Profiling
    • Pimp my Log
    • Filebeat
    • SSH Users
    • MySQL Users
    • Shopware Currency
  • Development
    • Intro
    • Start Developing
    • Switch Branches
    • Debugging
    • Watchers
    • App Development
    • Update Shopware
    • Dockware Essentials
    • Custom Domains
    • Custom Images
    • Code Coverage
    • CLI Build Shopware 6 Plugin
    • Multi-Environment Setups
  • Contribute
    • Intro
    • Setup Github Version
    • Create Feature
    • Code Styles
    • Testing
    • Create Pull Requests
  • CI/CD
    • Github
    • Gitlab
    • Bitbucket
    • Buddy
  • Tips & Tricks
    • Create a new Project
    • Bind-Mounting
    • Persisting Data
    • Housekeeping
    • Online Servers
    • Performance on Mac
    • Security
  • FAQ
    • Sequel Pro
    • Dockware and other images
    • Scripts (PSH?)
    • Redis
    • Error Port not available
    • MySQL failed
    • Elasticsearch
    • Windows Problems
    • Chrome Problems
    • Import MySQL Dump
    • Shopware 5 Support
    • Use Https/SSL
    • Container hangs in Pipeline
    • Disable the admin worker
  • Additional Links
    • Imprint
    • Founders
    • Dockware website
    • Dockware in Shopware Slack
Powered by GitBook
On this page
  • 1. Verify Docker Containers
  • 2. Verify other services

Was this helpful?

  1. FAQ

Error Port not available

If you start your container and you get an error such as this one, then it does only mean that you already have a service (or another Docker container) running on that port.

Ports are not available: listen tcp 0.0.0.0:80: bind: An attempt was made to access a socket 
in a way forbidden by its access permissions

"Localhost" along with the port of a container are the unique identifier in Docker. This means, that a container cannot be started if the port is already blocked.

To fix this please use these steps.

1. Verify Docker Containers

Check all your existing Docker containers and remove the one, that uses the port that you need for your new container.

# show ALL containers
docker ps -a

# remove our old container
docker rm -f (container_name)

2. Verify other services

If no Docker container uses your port, it might be a native service or another application. For example, a locally installed MySQL instance might already block our Port 3306, so Docker cannot use it.

#find port 80 usage on mac or linux
sudo lsof -i -n -P | grep :80

exmaple output: com.docke 743 myusername 77u IPv6 0xa05aaf696f157485 0t0 TCP *:80 (LISTEN)

In that case, make sure to either disable these services, or maybe use a different port for your Docker container if possible.

PreviousRedisNextMySQL failed

Last updated 4 years ago

Was this helpful?