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
•
21 Apr 2024
This command will help you spot any unusually large directories
The red flag was when I saw the server disk space is showing a site is taking up 57992.5 MB, where locally the site size is showing 957MB. There is something serious happening here and I need to establish the problem quickly. When dealing with a significant discrepancy in site size...
Andrew Fletcher
•
05 Apr 2024
Drupal 9 to 10 upgrade an example of the actual steps taken
Continuing on from the Drupal 9 to Drupal 10 upgrade outline written earlier... Upgrading Drupal 9 to Drupal 10. However, the point of difference is this article works through the actual action steps of the upgrade.Planning and testing is critical for the Drupal to version 10 process to...
Andrew Fletcher
•
18 Mar 2024
Resolving CVE-2022-48624 less issue
To resolve the CVE-2022-48624 vulnerability on Ubuntu using Nginx, it's crucial to understand that the issue lies within the "less" package, not Nginx itself. The vulnerability affects "less" before version 606, where close_altfile in filename.c in less omits shell_quote calls for LESSCLOSE,...