Open facundobringas opened 7 months ago
/cc @Karm (mandrel), @evanchooly (kotlin), @galderz (mandrel), @geoand (kotlin), @zakkak (mandrel)
FWIW I can't reproduce this on Linux x86_64. @galderz could you give it a go please?
What podman version are you running? All looks good to me on M1 with Quarkus 3.6.0 and the very latest podman install with brew, see output.
After installing podman I ran:
$ podman machine init -m 8092 --cpus 4
Extracting compressed file: podman-machine-default_fedora-coreos-39.20231119.2.0-qemu.aarch64.qcow2: done
Image resized.
Machine init complete
To start your machine run:
podman machine start
$ podman machine start
Starting machine "podman-machine-default"
Waiting for VM ...
Mounting volume... /Users:/Users
Mounting volume... /private:/private
Mounting volume... /var/folders:/var/folders
This machine is currently configured in rootless mode. If your containers
require root permissions (e.g. ports < 1024), or if you run into compatibility
issues with non-podman clients, you can switch using the following command:
podman machine set --rootful
API forwarding listening on: /Users/galder/.local/share/containers/podman/machine/qemu/podman.sock
The system helper service is not installed; the default Docker API socket
address can't be used by podman. If you would like to install it, run the following commands:
sudo /opt/homebrew/Cellar/podman/4.8.0/bin/podman-mac-helper install
podman machine stop; podman machine start
You can still connect Docker API clients by setting DOCKER_HOST using the
following command in your terminal session:
export DOCKER_HOST='unix:///Users/galder/.local/share/containers/podman/machine/qemu/podman.sock'
Machine "podman-machine-default" started successfully
@galderz, thanks on your input. I am using podman version 4.7.2. I also updated the bug description to include it.
@galderz this is my podman machine info output:
> podman machine info
Host:
Arch: arm64
CurrentMachine: podman-machine-default
DefaultMachine: podman-machine-default
EventsDir: /var/folders/wz/q9j66fx96433z_zfgdw9rftm0000gn/T/podman-run--1/podman
MachineConfigDir: /Users/facundolarrosa/.config/containers/podman/machine/qemu
MachineImageDir: /Users/facundolarrosa/.local/share/containers/podman/machine/qemu
MachineState: Stopped
NumberOfMachines: 1
OS: darwin
VMType: qemu
Version:
APIVersion: 4.7.2
Built: 1698753557
BuiltTime: Tue Oct 31 08:59:17 2023
GitCommit: 750b4c3a7c31f6573350f0b3f1b787f26e0fe1e3
GoVersion: go1.21.3
Os: darwin
OsArch: darwin/arm64
Version: 4.7.2
> podman machine start
Starting machine "podman-machine-default"
Waiting for VM ...
Mounting volume... /Users:/Users
Mounting volume... /private:/private
Mounting volume... /var/folders:/var/folders
This machine is currently configured in rootless mode. If your containers
require root permissions (e.g. ports < 1024), or if you run into compatibility
issues with non-podman clients, you can switch using the following command:
podman machine set --rootful
API forwarding listening on: /Users/facundolarrosa/.local/share/containers/podman/machine/qemu/podman.sock
The system helper service is not installed; the default Docker API socket
address can't be used by podman. If you would like to install it run the\nfollowing commands:
sudo /opt/homebrew/Cellar/podman/4.7.2/bin/podman-mac-helper install
podman machine stop/opt/homebrew/Cellar/podman/4.7.2/bin/podman-mac-helper; podman machine start/opt/homebrew/Cellar/podman/4.7.2/bin/podman-mac-helper
You can still connect Docker API clients by setting DOCKER_HOST using the
following command in your terminal session:
export DOCKER_HOST='unix:///Users/facundolarrosa/.local/share/containers/podman/machine/qemu/podman.sock'
Machine "podman-machine-default" started successfully
I was running 4.8.0
vs your 4.7.2
. You could try updating to 4.8.0
and see if that works.
The other thing you could do is re-creating the machine instance in case something has gone wrong with it, e.g. podman machine rm
and then create it again. Make sure the new machine has enough cpu and memory to do the native compilation.
Describe the bug
This is happening while following getting started steps from Quarkus documentation and easily reproduced as described.
Expected behavior
Class io.quarkus.runner.GeneratedMain should be found in classpath and build should complete without errors.
Actual behavior
Sample output:
How to Reproduce?
This is easily reproducible running the following commands:
Output of
uname -a
orver
Darwin 23.1.0 Darwin Kernel Version 23.1.0: Mon Oct 9 21:28:31 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T8112 arm64
Output of
java -version
Java 17.0.9
Mandrel or GraalVM version (if different from Java)
ubi-quarkus-mandrel-builder-image:jdk-21
Quarkus version or git rev
Quarkus 3.5.3
Build tool (ie. output of
mvnw --version
orgradlew --version
)Maven 3.9.5
Additional information
I am also using:
I have tried with other environment variables. It also happens using:
kotlin:
gradle
GraalVM image