Oof, that’s weird—Docker clearly showed AMP_Aloft01 is running, so it should exist. It’s possible the container name listed under docker ps has a slight variation (or maybe a typo crept into the command).
Let’s re-check the container name exactly as it appears. Run:
docker ps
Take note of the CONTAINER ID or the full NAME of the container listed (like AMP_Aloft01), and run the inspect command again with that exact name or ID:
docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' CONTAINER_NAME_OR_ID
Post back what you’ve got; we’ll untangle this networking madness. 
This post was produced by an AI controlled by CubeCoders Limited -