Using okteto locally without an image registry

[jgonera]

Hi,

I'd like to use Okteto as a replacement for Docker Compose by using it with a local Kubernetes cluster that comes with Docker Desktop. I tried both using existing docker-compose.yaml (although okteto had problems parsing my volumes) and okteto.yaml. The problem I run into is that Okteto, as opposed to Docker Compose, always tries to fetch Docker images from an external registry:

Error checking image at registry okteto.global/my-service-server:okteto-with-volume-mounts-0a6e3ab345045041941ae9834fff6be6b82a990d648eed42e9a92dc2f8ff5dc7: error checking image at registry okteto.global/my-service-server:okteto-with-volume-mounts-0a6e3ab345045041941ae9834fff6be6b82a990d648eed42e9a92dc2f8ff5dc7: error getting image tag with digest: error getting image digest: error getting image descriptor: Get "https://okteto.global/v2/": tcp dial failed for okteto.global:443: dial tcp: lookup okteto.global on 192.168.1.1:53: no such host

Is there a way to tell Okteto to only use local image cache, and if the image doesn't exist there, then build it using Dockerfile?

My okteto.yaml:

build:
  server:
    context: .
    target: base
dev:
  server:
    autocreate: true
    command: npm run dev
    environment:
      NODE_ENV: development
    forward:
      - 8080:8080
    sync:
      - .:/opt/app
      - ~/.aws:/root/.aws
    volumes:
      - /opt/app/node_modules

[jLopezbarb]

Hi @jgonera, which CLI version are you using? Can you try upgrading it and try again? We fixed an issue in the latest version

[jgonera]

Sorry for a slow reply. I get this now for the above config:

$ okteto up
 i  Using default @ docker-desktop as context
 x  'build.server.image' is required if your cluster doesn't have Okteto installed
$ okteto version
okteto version 2.16.4

Is there a way to make okteto build an image on demand?

[jLopezbarb]

Hi again @jgonera. You will need to specify where you want to build the image on the build section. So it will look like something like this:

build:
  server:
    context: .
    target: base
    image: jgonera/server:latest
dev:
  server:
    autocreate: true
    command: npm run dev
    environment:
      NODE_ENV: development
    forward:
      - 8080:8080
    sync:
      - .:/opt/app
      - ~/.aws:/root/.aws
    volumes:
      - /opt/app/node_modules

[jgonera]

I'm getting this now:

  i  Using default @ docker-desktop as context
 x  Error checking image at registry jgonera/server:latest: error checking image at registry jgonera/server:latest: error getting image tag with digest: error getting image digest: error getting image descriptor: GET https://index.docker.io/v2/jgonera/server/manifests/latest: UNAUTHORIZED: authentication required; [map[Action:pull Class: Name:jgonera/server Type:repository]]

I'd like to not use a remote registry at all, just locally build an image and start a container like Docker Compose does.

[jLopezbarb]

We don't have access to the local registry (at least for now), so the only way of using a custom image is pushing it to a registry. Another solution would be using Okteto cloud which uses a custom registry for every developer where he is the only one with access to it. In that case you don't need to specify the image tag on the build section

[jgonera]

Thank you. I understand there may be technical difficulties or it was just not the highest priority so far but Okteto would be a much easier sell for me if I could first run it first locally and then (when my dev env grows) switch to a cloud solution.