You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running "make create" appears to run successfully. I'm able to SSH into the cos-vm compute engine instance, but I notice when I run sudo docker ps that there are no associated processes on that instance:
Running make validate I'm returned with an error soon afterwards:
UDPATE
The issue appears to be that the image specified for the COS vm i.e. gcr.io/migration-to-containers/prime-flask:1.0.2. is not accessible.
The source code for the image is available in the repo under the directory: ~/gke-migration-to-containers/container. Was able to build it locally by SSHing into the COS vm and using: docker build -t gcr.io/migration-to-containers/prime-flask:1.0.2 .
Once built, I used the following docker run command to retrieve the local image and run it on the vm:
docker run --rm -d --name=appuser -p 8080:8080 gcr.io/migration
-to-containers/prime-flask:1.0.2
The text was updated successfully, but these errors were encountered:
Running "make create" appears to run successfully. I'm able to SSH into the cos-vm compute engine instance, but I notice when I run sudo docker ps that there are no associated processes on that instance:
Running make validate I'm returned with an error soon afterwards:
UDPATE
The issue appears to be that the image specified for the COS vm i.e. gcr.io/migration-to-containers/prime-flask:1.0.2. is not accessible.
The source code for the image is available in the repo under the directory: ~/gke-migration-to-containers/container. Was able to build it locally by SSHing into the COS vm and using: docker build -t gcr.io/migration-to-containers/prime-flask:1.0.2 .
Once built, I used the following docker run command to retrieve the local image and run it on the vm:
docker run --rm -d --name=appuser -p 8080:8080 gcr.io/migration
-to-containers/prime-flask:1.0.2
The text was updated successfully, but these errors were encountered: