-
Notifications
You must be signed in to change notification settings - Fork 110
can't pull latest container image for pod process #16
Comments
pod/process-XXX uses the same image as the master process. For the master process, you specify the image when you launch it. Could you describe the issue a little bit more in detail? Things like how did you run your code, what docker image is expected what docker image is actually used would be very helpful. |
i use this command to run the job kubectl create job fiber-test --image=<hub_name>/fiber-testing -- python3 /root/run.py let say first time i run this job with <hub_name>/fiber-testing , then i build and push the new image . it still use back the old container image |
After you build and push image, do you still use Can verify that you launch fiber master process with the correct image? Seems more like to be running |
@calio of course i ran the command again =) i know there is somewhere need to set this imagePullPolicy=Always, can you point me to the source code where it script use to create pod/process-xxx |
OK, here is the place where new pod is created https://github.com/uber/fiber/blob/master/fiber/kubernetes_backend.py#L117 |
when running in kubernetes, the pod/process-XXX does not pull the latest new image. May i know which file in this repo that use to create pod/process-XXX ?
The text was updated successfully, but these errors were encountered: