Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

500 error during cfs-locked - downloaded binary #35

Open
qisback opened this issue Aug 9, 2020 · 5 comments
Open

500 error during cfs-locked - downloaded binary #35

qisback opened this issue Aug 9, 2020 · 5 comments
Labels
question Further information is requested

Comments

@qisback
Copy link

qisback commented Aug 9, 2020

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
Copy link

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

@dot-mike
Copy link

Can confirm, need to rebuild binary.

Manual build from source working 100%

@lnxbil
Copy link
Owner

lnxbil commented Sep 24, 2020

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?

@lnxbil lnxbil added the question Further information is requested label Sep 30, 2020
@nnps255
Copy link

nnps255 commented Oct 7, 2020

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
Copy link
Owner

lnxbil commented Oct 7, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

5 participants