Sj-g opened a new issue, #16785:
URL: https://github.com/apache/dolphinscheduler/issues/16785

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   I used the file parameter passing example on the official website, but I 
couldn't pass the parameters. I used the docker pseudo-distributed setup and 
configured minio on the resource center. The file could be uploaded normally. 
Here is the log of the problem:
   
![image](https://github.com/user-attachments/assets/740b27dd-1ad7-4d96-8957-7bc549713c1e)
   
![image](https://github.com/user-attachments/assets/97387d6f-bf53-44f3-833a-e9627d24e3a9)
   The above figure shows that the output is uploaded successfully
   
![image](https://github.com/user-attachments/assets/ae582059-7bff-400d-91f6-3e1fdc7cc1d2)
   Let me check if the key value is correct, I also double checked
   
   
![image](https://github.com/user-attachments/assets/87ea161c-d0fe-46c2-9b1a-5203b581a037)
   
![image](https://github.com/user-attachments/assets/48084b3e-15c8-495d-beef-8b2f81adb927)
   I also check the file upload
   
![image](https://github.com/user-attachments/assets/bfa1b890-9688-4f3a-b553-44f0b696e2b2)
   I currently don't know where the error is
   
   ### What you expected to happen
   
   File parameters can be passed normally
   
   ### How to reproduce
   
   Use the pseudo-distributed deployment of docker deployment in the official 
documentation
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.2.x
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: 
[email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to