500 error during cfs-locked - downloaded binary

[qisback]

v4 binary fails with error:

(rancher) ---------------------- RESPONSE LOG -----------------------
(rancher) STATUS : 500 error during cfs-locked 'storage-docker-data' operation: illegal name 'vm--disk-0' - should be 'vm-103-*'
(rancher) RECEIVED AT : 2020-08-09T20:25:37.949677272+01:00
(rancher) RESPONSE TIME : 14.709889ms
(rancher) HEADERS:
(rancher) Cache-Control: max-age=0
(rancher) Content-Length: 13
(rancher) Content-Type: application/json;charset=UTF-8
(rancher) Date: Sun, 09 Aug 2020 19:25:37 GMT
(rancher) Expires: Sun, 09 Aug 2020 19:25:37 GMT
(rancher) Pragma: no-cache
(rancher) Server: pve-api-daemon/3.0
(rancher) BODY :
(rancher) {
(rancher) "data": null
(rancher) }
(rancher) ----------------------------------------------------------

however ID lookup shows

(rancher) BODY :
(rancher) {
(rancher) "data": "103"
(rancher) }

Cloning MASTER and compiling does not have this issue.

(rancher) ---------------------- RESPONSE LOG -----------------------
(rancher) STATUS : 200 OK
(rancher) RECEIVED AT : 2020-08-09T20:44:24.871733238+01:00
(rancher) RESPONSE TIME : 214.399028ms
(rancher) HEADERS:
(rancher) Cache-Control: max-age=0
(rancher) Content-Length: 36
(rancher) Content-Type: application/json;charset=UTF-8
(rancher) Date: Sun, 09 Aug 2020 19:44:24 GMT
(rancher) Expires: Sun, 09 Aug 2020 19:44:24 GMT
(rancher) Pragma: no-cache
(rancher) Server: pve-api-daemon/3.0
(rancher) BODY :
(rancher) {
(rancher) "data": "docker-data:vm-103-disk-0"
(rancher) }
(rancher) ----------------------------------------------------------

[mbchristoff]

Same here, when using local storage the api call doesn't fail but the name becomes: local:208/vm--disk-0.raw

[dot-mike]

Can confirm, need to rebuild binary.

Manual build from source working 100%

[lnxbil]

Hmm, don't really get this, but nice that it works, at least in the code. Have you used the Makefile?

I reuploaded the binaries compiled with go 1.15.2. I do not have a CIFS test environment at the moment, so I have to rely on you guys to check this out. Could you please try?

[nnps255]

Hi,
I am newbies.. please let me know how to use this. I know how to run the script.sh file. but how to use the docker-machine-driver-proxmoxve.linux-amd64 file.

[lnxbil]

I am newbies.. please let me know how to use this. I know how to run the script.sh file. but how to use the docker-machine-driver-proxmoxve.linux-amd64 file.

You cannot invoke the binary directly, you have to go through docker-machine. Its official documentation is here. The Proxmox VE specific arguments to create a docker machine are shown with docker-machine create --driver proxmoxve --help