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
Before you start
According to this issue GNS3/gns3-web-ui#951 GNS3 should support fractional values for limiting CPU usage in Docker containers
cpus: maximum amount of CPU resources the container can use (float), for instance 0.5 will limit the container to 50% of a CPU core.
Describe the bug
When trying to use a fractional values for Maximum CPUs on the Docker container configuration page an error is displayed.
GNS3 version and operating system (please complete the following information):
OS: ArchLinux (Python 3.11.8 )
GNS3 version 3.0.0 beta1
GNS3 is installed on bare metal (no GNS3 VM)
To Reproduce
Steps to reproduce the behavior:
Drag a Docker container on the topology, right click and select Configure
In the Maximum CPU list type a fractional value like 0,5
Click on Apply to save the changes
The following error is displayed in the console.
HTTP error 422 received from compute ' (controller)' for request
PUT /projects/696bf903-ecf1-460b-92ba-3f3976db0967/docker/nodes/26bff5f6-67f2-4409-accf-5eddefee48f9:
{"detail":[{"type":"int_from_float","loc":["body","cpus"],
"msg":"Input should be a valid integer, got a number with a fractional part",
"input":0.5000000000000001,
"url":"https://errors.pydantic.dev/2.1.2/v/int_from_float"}]}
Screenshots or videos
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Before you start
According to this issue GNS3/gns3-web-ui#951 GNS3 should support fractional values for limiting CPU usage in Docker containers
Describe the bug
When trying to use a fractional values for Maximum CPUs on the Docker container configuration page an error is displayed.
GNS3 version and operating system (please complete the following information):
To Reproduce
Steps to reproduce the behavior:
Screenshots or videos
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: