You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows installs the desktop version of docker, and docker binds the port. Windows cannot access through ip and port.
Windows installs the desktop version of Docker, and Docker binds the port. Windows cannot be accessed through IP and port. I changed the port to a different one and turned off the Windows firewall. The same docker version can access the port without any problem on another Windows. What is the reason? I have searched for the answer countless times but to no avail. It runs well under Linux.
docker run -d -p %port%:%container_port% --gpus all --name %container_name% -it -v "%cd%:/app" %image_name% -e HOST=%container_ip% -e PORT=%container_port% -e MODEL=%model_path%
Expected behavior
No response
docker version
Version: 24.0.6
docker info
(base) PS C:\Users\Admin> docker info
Client:
Version: 24.0.6
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.11.2-desktop.5
Path: C:\Program Files\Docker\cli-plugins\docker-buildx.exe
compose: Docker Compose (Docker Inc.)
Version: v2.23.0-desktop.1
Path: C:\Program Files\Docker\cli-plugins\docker-compose.exe
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.0
Path: C:\Program Files\Docker\cli-plugins\docker-dev.exe
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.20
Path: C:\Program Files\Docker\cli-plugins\docker-extension.exe
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v0.1.0-beta.9
Path: C:\Program Files\Docker\cli-plugins\docker-init.exe
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: C:\Program Files\Docker\cli-plugins\docker-sbom.exe
scan: Docker Scan (Docker Inc.)
Version: v0.26.0
Path: C:\Program Files\Docker\cli-plugins\docker-scan.exe
scout: Docker Scout (Docker Inc.)
Version: v1.0.9
Path: C:\Program Files\Docker\cli-plugins\docker-scout.exe
Server:
Containers: 2
Running: 1
Paused: 0
Stopped: 1
Images: 4
Server Version: 24.0.6
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 8165feabfdfe38c65b599c4993d227328c231fca
runc version: v1.1.8-0-g82f18fe
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
Kernel Version: 5.15.133.1-microsoft-standard-WSL2
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 20
Total Memory: 15.51GiB
Name: PS2022NANPACRT
ID: 355ba1d0-adf3-47d9-83bf-19a585576895
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
127.0.0.0/8
Registry Mirrors:
https://registry.docker-cn.com/
http://hub-mirror.c.163.com/
https://docker.mirrors.ustc.edu.cn/
https://cr.console.aliyun.com/
https://mirror.ccs.tencentyun.com/
https://ustc-edu-cn.mirror.aliyuncs.com/
Live Restore Enabled: false
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: daemon is not using the default seccomp profile
Diagnostics ID
无法生成
Additional Info
Windows installs the desktop version of docker, and docker binds the port. Windows cannot access through ip and port.
Windows installs the desktop version of Docker, and Docker binds the port. Windows cannot be accessed through IP and port. I changed the port to a different one and turned off the Windows firewall. The same docker version can access the port without any problem on another Windows. What is the reason? I have searched for the answer countless times but to no avail. It runs well under Linux.
The text was updated successfully, but these errors were encountered:
@CHminggao
After updating Windows 10 to version 21H2, everything has become smoother, but docker takes up too much memory. How to solve this problem?
Solve the problem of high memory usage of Vmmem when installing Docker for Windows
Description
Windows installs the desktop version of docker, and docker binds the port. Windows cannot access through ip and port.
Windows installs the desktop version of Docker, and Docker binds the port. Windows cannot be accessed through IP and port. I changed the port to a different one and turned off the Windows firewall. The same docker version can access the port without any problem on another Windows. What is the reason? I have searched for the answer countless times but to no avail. It runs well under Linux.
Reproduce
@echo off
set image_name="yolo_detect:v2"
set container_name="yolo_detect"
set port=6800
set container_port=6800
set container_ip="0.0.0.0"
set model_path="best.pt"
for /f %%i in ('docker images -q %IMAGE_NAME%') do docker rmi %%i
for /f %%i in ('docker ps -aq --filter "name=%CONTAINER_NAME%"') do docker rm %%i
docker build -t %image_name% -f Dockerfile-windows-pytorch .
docker run -d -p %port%:%container_port% --gpus all --name %container_name% -it -v "%cd%:/app" %image_name% -e HOST=%container_ip% -e PORT=%container_port% -e MODEL=%model_path%
Expected behavior
No response
docker version
docker info
Diagnostics ID
无法生成
Additional Info
Windows installs the desktop version of docker, and docker binds the port. Windows cannot access through ip and port.
Windows installs the desktop version of Docker, and Docker binds the port. Windows cannot be accessed through IP and port. I changed the port to a different one and turned off the Windows firewall. The same docker version can access the port without any problem on another Windows. What is the reason? I have searched for the answer countless times but to no avail. It runs well under Linux.
The text was updated successfully, but these errors were encountered: