I feel love I’ve written a post on this before, but it doesn’t hurt to keep things upto date.<\/p>\n
I set up a Kubernetes instance along with container registry etc. within Azure, but if all you want to do is run things locally and at zero cost (other than you usual cost of running a computer), you might want to set up a local container registry.<\/p>\n
I’m doing this on Windows for this post, but I expect it’s pretty much the same on Linux and Mac, but in my case I am also running Docker Desktop.<\/p>\n
docker-compose<\/strong><\/p>\n We’re going to stand up the registry using docker-compose, but if you’d like to just run the registry from the simple docker run command, you can use this<\/p>\n However you’ll probably want a volume set-up, along with a web UI, so let’s put all that together into the docker-compose.yml<\/em> file below<\/p>\n Note: if you’re going to be running your services on port 8080, you might wish to change the UI here to use port 8081, for example.<\/em><\/p>\n In the above I name my container container-registry<\/em> as I already have a registry<\/em> container running on my machine, the REGISTRY_HTTP_HEADERS_Access were required as I was getting CORS like issues. Finally we run up the To run everything just type<\/p>\n and use ctrl+c to bring this down when in interactive mode or run<\/p>\n If you want to clear up the volume (i.e. remove it) use <\/p>\n Ofcourse you can also use curl etc. to interact with the registry itself, for example to list the repositories<\/p>\n Tag and push<\/strong><\/p>\n We’re obviously going to need to push images to the registry and this is done by first, tagging them (as usual) then pushing, so for example<\/p>\n which tags the image I already created for a simple “echo service”.<\/p>\n Next we push the tagged image to the registry using<\/p>\n If you’re running the web UI you should be able to see the repository with your new tagged image.<\/p>\n Pull<\/strong><\/p>\n Obviously we’ll want to be able to pull an image from the registry either to run locally or to deploy within a Kubernetes cluster etc. <\/p>\n Deployment<\/strong><\/p>\n If some coming posts I will be writing an echo service in multiple languages, so let’s assume this echo_services is one of those. We’re going to want to run things locally so we might have a deployments.yaml with the following deployment and service<\/p>\n Now we can use port forwarding in place on an ingress service if we’d like, for testing, like this<\/p>\n and now use http:\/\/localhost:8080\/echo?text=Putridparrot<\/em><\/p>\n Other options to get this deployment running with ingress require hosts<\/em> file changes or we can add a load balancer, for example<\/p>\n I feel love I’ve written a post on this before, but it doesn’t hurt to keep things upto date. I set up a Kubernetes instance along with container registry etc. within Azure, but if all you want to do is run things locally and at zero cost (other than you usual cost of running a […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[102],"tags":[],"class_list":["post-11573","post","type-post","status-publish","format-standard","hentry","category-docker"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/11573","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/comments?post=11573"}],"version-history":[{"count":5,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/11573\/revisions"}],"predecessor-version":[{"id":11581,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/11573\/revisions\/11581"}],"wp:attachment":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/media?parent=11573"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/categories?post=11573"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/tags?post=11573"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\r\ndocker run -d -p 5000:5000 --name registry registry:2\r\n<\/pre>\n
\r\nversion: '3.8'\r\n\r\nservices:\r\n registry:\r\n image: registry:2\r\n container_name: container-registry\r\n ports:\r\n - "5000:5000"\r\n environment:\r\n REGISTRY_STORAGE_FILESYSTEM_ROOTDIRECTORY: \/var\/lib\/registry\r\n REGISTRY_HTTP_HEADERS_Access-Control-Allow-Origin: '["http:\/\/localhost:8080"]'\r\n REGISTRY_HTTP_HEADERS_Access-Control-Allow-Methods: '["GET", "HEAD", "DELETE"]'\r\n REGISTRY_HTTP_HEADERS_Access-Control-Allow-Credentials: '["true"]'\r\n volumes:\r\n - registry-data:\/var\/lib\/registry\r\n\r\n registry-ui:\r\n image: joxit\/docker-registry-ui:latest\r\n container_name: registry-ui\r\n ports:\r\n - "8080:80"\r\n environment:\r\n - REGISTRY_TITLE=Private Docker Registry\r\n - REGISTRY_URL=http:\/\/localhost:5000\r\n - DELETE_IMAGES=true\r\n depends_on:\r\n - registry\r\n\r\nvolumes:\r\n registry-data:\r\n<\/pre>\n
\r\ndocker-compose up\r\n<\/pre>\n
\r\ndocker-compose down\r\n<\/pre>\n
\r\ndocker-compose down -v\r\n<\/pre>\n
\r\ncurl http:\/\/localhost:500\/v2\/_catalog\r\n<\/pre>\n
\r\ndocker tag putridparrot.echo_service:v1 localhost:5000\/putridparrot.echo_service:v1\r\n<\/pre>\n
\r\ndocker push localhost:5000\/putridparrot.echo_service:v1\r\n<\/pre>\n
\r\ndocker pull localhost:5000\/putridparrot.echo_service:v1\r\n<\/pre>\n
\r\napiVersion: apps\/v1\r\nkind: Deployment\r\nmetadata:\r\n name: echo\r\n namespace: dev\r\n labels:\r\n app: echo\r\nspec:\r\n replicas: 1\r\n selector:\r\n matchLabels:\r\n app: echo\r\n template:\r\n metadata:\r\n labels:\r\n app: echo\r\n spec:\r\n containers:\r\n - name: echo\r\n image: localhost:5000\/putridparrot.echo_service:v1\r\n ports:\r\n - containerPort: 8080\r\n resources:\r\n requests:\r\n memory: "100Mi"\r\n cpu: "100m"\r\n limits:\r\n memory: "200Mi"\r\n cpu: "200m"\r\n livenessProbe:\r\n httpGet:\r\n path: \/livez\r\n port: 8080\r\n initialDelaySeconds: 30\r\n periodSeconds: 10\r\n readinessProbe:\r\n httpGet:\r\n path: \/readyz\r\n port: 8080\r\n initialDelaySeconds: 5\r\n periodSeconds: 5\r\n\r\n---\r\napiVersion: v1\r\nkind: Service\r\nmetadata:\r\n name: echo-service\r\n namespace: dev\r\n labels:\r\n app: echo\r\nspec:\r\n type: ClusterIP\r\n selector:\r\n app: echo \r\n ports:\r\n - name: http\r\n port: 80\r\n targetPort: 8080\r\n protocol: TCP\r\n<\/pre>\n
\r\nkubectl port-forward svc\/echo-service 8080:8080 -n dev\r\n<\/pre>\n
\r\napiVersion: v1\r\nkind: Service\r\nmetadata:\r\n name: echo-service\r\nspec:\r\n type: LoadBalancer\r\n selector:\r\n app: echo\r\n ports:\r\n - protocol: TCP\r\n port: 8080\r\n targetPort: 8080\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"