Well, even if you deploy to a local server on-prem, you would still need to use a container registry (either on-cloud or on-prem) to host your images that then docker can pull.
There is a "workaround" but I do not endorse it. When you have your imaged built and saved in the tar file using docker save, then you could copy that tar file to your target server and re-hydrate the image using docker load... this way you'd have the image directly on the server and you wouln't need a registry.
Once again, I do not recommend nor endorse this approach :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the feedback :)
Well, even if you deploy to a local server on-prem, you would still need to use a container registry (either on-cloud or on-prem) to host your images that then docker can pull.
There is a "workaround" but I do not endorse it. When you have your imaged built and saved in the tar file using
docker save
, then you could copy that tar file to your target server and re-hydrate the image usingdocker load
... this way you'd have the image directly on the server and you wouln't need a registry.Once again, I do not recommend nor endorse this approach :)