Hi,
Every containers have the same problem. Maybe I forgot to do something but it's strange.
Thx.
Docker and Network
- nytwordlehints
- Posts: 1
- Joined: 23 Oct 2024, 16:23

Re: Docker and Network
You can create a custom Docker network with the desired IP range (e.g., 192.168.1.0/24), then start a container within that network specifying a specific IP address (e.g., 192.168.1.200). This allows you to have containers with customized IP addresses in Docker.
Re: Docker and Network
But, surely, the docker network cannot have the same segment address as the local lan?nytwordlehints wrote: ↑23 Oct 2024, 16:25 You can create a custom Docker network with the desired IP range (e.g., 192.168.1.0/24), then start a container within that network specifying a specific IP address (e.g., 192.168.1.200). This allows you to have containers with customized IP addresses in Docker.
F5-221 TOS7.0.0777 - 4x4TB (Ironwolf) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid

