Error with Docker setup using Podman in Datahub - Seeking advice on resolving build container issues

Original Slack Thread

Hello sir, I have some error in datahub gradlew quickstartDebug.

need to some change configuration in my local…?

Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: error creating build container: short-name "golang:1-alpine3.18" did not resolve to an alias and no unqualified-search registries are defined in "/etc/containers/registries.conf"

> Task :metadata-service:war:cleanLocalDockerImages
Docker image string: linkedin/datahub-gms:v0.12.1rc2-SNAPSHOT
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.

> Task :docker:elasticsearch-setup:docker FAILED
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
[1/5] STEP 1/8: FROM golang:1-alpine3.18 AS binary
[2/5] STEP 1/5: FROM alpine:3 AS base
Error: error creating build container: short-name "golang:1-alpine3.18" did not resolve to an alias and no unqualified-search registries are defined in "/etc/containers/registries.conf"

> Task :docker:kafka-setup:docker FAILED
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
[1/2] STEP 1/4: FROM confluentinc/cp-base-new:7.4.1 AS confluent_base
[2/2] STEP 1/36: FROM python:3-alpine
Error: error creating build container: short-name "confluentinc/cp-base-new:7.4.1" did not resolve to an alias and no unqualified-search registries are defined in "/etc/containers/registries.conf"```

Hey Jinyoung, we haven’t seen this error before in the Community - it looks like it’s an error related to Podman… I’m not familiar with deploying via Podman, but I suggest searching our Slack for podman to see if there are other threads that might lead you in the right direction