Skip to content

invalid FROM on native-micro #48102

@vsevel

Description

@vsevel

Describe the bug

when I create a new application, Dockerfile.native-micro contains:

# The `quay.io/quarkus/quarkus-micro-image:2.0` base image is based on UBI 9.
# To use UBI 8, switch to `quay.io/quarkus/quarkus-micro-image:2.0`.
###
FROM quay.io/quarkus/quarkus-micro-image:2.0

you probably meant:

# The `quay.io/quarkus/ubi9-quarkus-micro-image:2.0` base image is based on UBI 9.
# To use UBI 8, switch to `quay.io/quarkus/quarkus-micro-image:2.0`.
###
FROM quay.io/quarkus/ubi9-quarkus-micro-image:2.0

the native dockerfile seems off as well:

# The ` registry.access.redhat.com/ubi8/ubi-minimal:8.10` base image is based on UBI 9.
# To use UBI 8, switch to `quay.io/ubi8/ubi-minimal:8.10`.
###
FROM registry.access.redhat.com/ubi8/ubi-minimal:8.10

this should probably be:

# The ` **registry.access.redhat.com/ubi9/ubi-minimal:9.5`** base image is based on UBI 9.
# To use UBI 8, switch to `quay.io/ubi8/ubi-minimal:8.10`.
###
FROM registry.access.redhat.com/ubi9/ubi-minimal:9.5

and I am not sure about the 2 registries quay and registry.access.redhat.com
which one do we want?

cc @ia3andy

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

create a new application

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

3.22.3

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions