-
Notifications
You must be signed in to change notification settings - Fork 8k
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
Gin SetMode not Passing Value to Function, Cause Panic Error On Minikube/Microk8s #4023
Comments
The default is gin.DebugMode, which can be manually specified package main
import "github.com/gin-gonic/gin"
func main() {
gin.SetMode(gin.DebugMode)
r := gin.Default()
r.GET("/", func(c *gin.Context) {
c.JSON(200,gin.H{"msg":"ok"})
})
r.Run(":9000")
} [GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached.
[GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production.
- using env: export GIN_MODE=release
- using code: gin.SetMode(gin.ReleaseMode)
[GIN-debug] GET / --> main.main.func1 (3 handlers)
[GIN-debug] [WARNING] You trusted all proxies, this is NOT safe. We recommend you to set a value.
Please check https://pkg.go.dev/github.com/gin-gonic/gin#readme-don-t-trust-all-proxies for details.
[GIN-debug] Listening and serving HTTP on :9000 go version go1.21.7 linux/amd64 |
hi RedCrazyGhost, thank for reply. in common linux, or windows or docker container, when I try run go gin with my code above, its normal work with no problem, but I try on kubernetes in microk8s and minikube its error happen. I even try enter to the exec on pods and run from there, but still error, I also debug on gin SetMode function for see what happen, and I found param not pass to the function. |
Description
this problem happen when I try to create pods on microk8s. gin setMode cannot pass the value from main.go. so, output return panic. I also try on minkube but the result same
How to reproduce
Expectations
Actual result
Environment
The text was updated successfully, but these errors were encountered: