October-16th-2018, 06:07 PM
I have also ran into this issue (after setting the time, checking for port 5000 and copy/paste from the readme).
I was able to start the container only after I went to /portainer/#/images/ and pulled the image before attempting to create/start the container.
Is that correct, or should you be able to create a container without a local image? Is there a timeout issue with pulling the image when creating the container?
Thank you
Steve
I was able to start the container only after I went to /portainer/#/images/ and pulled the image before attempting to create/start the container.
Is that correct, or should you be able to create a container without a local image? Is there a timeout issue with pulling the image when creating the container?
Thank you
Steve