Date : 04/09/2024 Logs

deadpool@LIN-5CG1153HDQ:/mnt/c/Users/adhakre/Downloads/timecard (1)/timecard$ docker build -t timecard . Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg. STEP 1/5: FROM amazoncorretto:17 Error: error creating build container: short-name "amazoncorretto:17" did not resolve to an alias and no unqualified-search registries are defined in "/etc/containers/registries.conf" deadpool@LIN-5CG1153HDQ:/mnt/c/Users/adhakre/Downloads/timecard (1)/timecard$ docker build -t timecard . Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg. STEP 1/5: FROM amazoncorreto:17 Error: error creating build container: short-name "amazoncorreto:17" did not resolve to an alias and no unqualified-search registries are defined in "/etc/containers/registries.conf" deadpool@LIN-5CG1153HDQ:/mnt/c/Users/adhakre/Downloads/timecard (1)/timecard$ docker build -t timecard . Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg. STEP 1/5: FROM amazoncorretto:17 Error: error creating build container: short-name "amazoncorretto:17" did not resolve to an alias and no unqualified-search registries are defined in "/etc/containers/registries.conf" deadpool@LIN-5CG1153HDQ:/mnt/c/Users/adhakre/Downloads/timecard (1)/timecard$ cat /etc/containers/registries.conf

For more information on this configuration file, see containers-registries.conf(5).

NOTE: RISK OF USING UNQUALIFIED IMAGE NAMES

We recommend always using fully qualified image names including the registry

server (full dns name), namespace, image name, and tag

(e.g., registry.redhat.io/ubi8/ubi:latest). Pulling by digest (i.e.,

quay.io/repository/name@digest) further eliminates the ambiguity of tags.

When using short names, there is always an inherent risk that the image being

pulled could be spoofed. For example, a user wants to pull an image named

foobar from a registry and expects it to come from myregistry.com. If

myregistry.com is not first in the search list, an attacker could place a

different foobar image at a registry earlier in the search list. The user

would accidentally pull and run the attacker's image and code rather than the

intended content. We recommend only adding registries which are completely

trusted (i.e., registries which don't allow unknown or anonymous users to

create accounts with arbitrary names). This will prevent an image from being

spoofed, squatted or otherwise made insecure. If it is necessary to use one

of these registries, it should be added at the end of the list.