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
to devcontainer.json results in failure to unmarshall json from string. Logs here:
[22:55:15] info #13 50.68 checking size of wchar_t... 4
[22:51:08] info Workspace d2 already exists
[22:51:09] info Creating devcontainer...
[22:51:12] info devcontainer up: parsing devcontainer.json: json: cannot unmarshal string into Go struct field HostRequirements.hostRequirements.gpu of type bool
[22:51:12] info error parsing workspace info: rerun as root: exit status 1
[22:51:12] error Try enabling Debug mode under Settings to see a more verbose output
[22:51:12] fatal run agent command: Process exited with status 1
What did you expect to happen instead?
As per official specs the hostRequirements.gpu can be string too. In this case it will be best effort ie, fallback to CPU only in case GPU provisioning fails.
How can we reproduce the bug? (as minimally and precisely as possible)
As above.
Local Environment:
DevPod Version: v0.4.2
Operating System: windows
ARCH of the OS: AMD64
DevPod Provider:
Cloud Provider: aws
Kubernetes Provider: N/a
Local/remote provider: ssh
Custom provider: provide imported provider.yaml config file: N/a
Anything else we need to know?
N/a
The text was updated successfully, but these errors were encountered:
What happened?
Passing
to
devcontainer.json
results in failure to unmarshall json from string. Logs here:What did you expect to happen instead?
As per official specs the
hostRequirements.gpu
can be string too. In this case it will be best effort ie, fallback to CPU only in case GPU provisioning fails.How can we reproduce the bug? (as minimally and precisely as possible)
As above.
Local Environment:
DevPod Provider:
provider.yaml
config file: N/aAnything else we need to know?
N/a
The text was updated successfully, but these errors were encountered: