PSA: Connections Issues with Docker Desktop 4.47.0 / 4.48.0

Hosting Containers
#1

Just a heads up:

There is some type of issue in Docker Desktop 4.47.0 and 4.48.0 (at least in Windows) where you may experience difficulties trying to connect to container webpages. For instance:

  • Firefox: All containers could connect, but would take 5-20 minutes to load the webpage.
  • Chrome: Had no issue with about 75% of containers, but others could never load.
  • Visual Studios/Python (including SLM): Took about 6 minutes to connect to a Channels Docker containers, but all others were no problem.
  • Channels DVR backend: Didn't seem to have issues, including connecting to the another Channels Docker container.

I was able to resolve the problem (after beating my head against a wall for hours and hours) by simply downgrading to Docker Desktop 4.46.0. As such, I highly recommend staying at this version or below!

#2

I noticed a issue with the latest version of DD where the the port numbers for containers were showing as in use when they were not. Not sure if this is the issue you are having. Mine cleared out after a restart to computer and docker restart on latest Docker Desktop 4.48.0

#3

Sounds like a different issue, or perhaps something else that happened in this version. This is the one closest to my experience:

I did many, many reboots, including a whole network shutdown for half an hour to clear everything out. I even rolled back Windows updates and some other stuff. Everything else held equal, only going back to DD 4.46.0 reset everything to baseline working perfectly.

1 Like
#4

I upgraded to 4.71 and now Docker keeps failing. How do I downgrade to 4.46?

#5

I downloaded the install file for 4.46, but I don't want to loose all of my setup stuff.

#6

You won't loose anything, you just install the file at that version and it overwrites your Docker Desktop application, not your Images/Containers. However, this is a pretty old thread. I'm on 4.7.0 and having no issue, so for this and any future situation, I recommend just going back as few a version as possible.

#7

My problem does not seem to be version related. I am back to version 4.59 and the problem still exists.

My virtual disk file keeps increasing in size, and compacting it only ever gets back a small amount of space.

It keeps increasing, even with no containers are running.

All of the on-line stuff I have found talks about compacting the VHD, but this is not working for me.

I don't know what to do, other than to reload the VHD from backup every few days.

I'm running Windows 10 Pro. Does anyone have any ideas.

#8

You already have a separate thread about that subject, let's not take over this one:

@chDVRuser already linked you to my documentation around this issue.