Replies: 2 comments
-
Because you're importing and using the package, it must be present for evaluation to complete. If you cache the package into your image, it won't need to be downloaded in the field. You can perform this caching by adding this to your Dockerfile: RUN pkl eval package://pkg.pkl-lang.org/pkl-go/pkl.golang@0.5.0#/go.pkl I would recommend doing this for any known Pkl package dependencies to avoid the need to download those packages at runtime |
Beta Was this translation helpful? Give feedback.
0 replies
-
Awesome, thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, I have a pkl module that includes
that allows us to codegen the Go code for the pkl module.
In our main.go, we have something like
We deploy this code into our IoT devices that have varying levels of internet connectivity. Occasionally, we see the following error:
Can someone help me understand why we need to download the go package at runtime? Also, we have noticed that if we restart our Docker container on the device, this error goes away.
Beta Was this translation helpful? Give feedback.
All reactions