Andrew Fletcher published: 22 January 2022 1 minute read
Resetting Docker is basically following the start parameters. All containers removed -
No containers running
Try running a container: Copy and paste this command into your terminal
docker run -d -p 80:80 docker/getting-started
Unable to find image 'docker/getting-started:latest' locally latest: Pulling from docker/getting-started
Error in set up
docker: Error response from daemon: Ports are not available: listen tcp 0.0.0.0:80: bind: address already in use.
Port checking
Lsof
Command: lsof -i -P
Do not combine the two parameters, like “-iP”, to avoid misinterpretation by lsof.
Use sudo to include all the ports owned by system processes
For more details, run man lsof
Related articles
Andrew Fletcher
•
16 Jan 2025
get IP address from terminal OSX
When troubleshooting network issues or configuring devices, knowing your IP address can be essential. Whether you're connected via Wi-Fi, Ethernet, or tethering through a mobile provider, macOS offers powerful built-in tools to quickly identify your IP address. Here's a practical guide tailored to...
Andrew Fletcher
•
07 Jan 2025
Managing DDEV environment troubleshooting and setting up multiple Drupal projects
DDEV has become a popular tool for local web development, offering a streamlined approach to managing Docker-based environments. However, setting up and managing DDEV projects, particularly with the latest versions of Docker Desktop, can present challenges. This article guides you through resolving...
Andrew Fletcher
•
28 Dec 2024
Optimising file transfers by improving efficiency from cp to rsync
Transferring files between development and production environments is a critical task in the deployment process. However, I continue to come across multiple approaches that scale from awesome automation using pipelines to the basic of direct command line entry. Where the basic approaches rely on...