Closed PunkFleet closed 3 months ago
@PunkFleet I've tried to repro this issue on my M2 Pro chip with macOS 14.5 and I was not able to get it to get stuck as reported, for me every time I tried to build the provided container file with AMD64 arch the build terminated with an error:
[2/4] STEP 4/5: COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* ./ Error:building at STEP "COPY package.json yarn.lock* package-lock.json* pnpm-lock.yaml* ./": checking on sources under "/var/tmp/libpod_builder1949777752/build": copier: stat: "/package.json": no such file or directory
But otherwise Podman Desktop seemed to be acting normally.
I've searched tons of information and haven't been able to fix it. Eventually I decided to replace the ISP's server with an intel architecture😥
Issue not reproducible, errors seems to be caused by incorrect container file.
Bug description
When using desktop on a m2 pro chip and choosing to build an image -> build -> amd64 architecture image, it gets stuck in the build session indefinitely.
Operating system
macOS 14.4.1 (23E224) Sonoma
Installation Method
Brew (macOS)
Version
1.11.0
Steps to reproduce
For testing, I created a new initial nextjs project and provided a Containerfile file to generate the image, but I would get stuck in the npm run build session forever. There were no errors during that time, and clicking the close or cancle button in the desktop didn't help, and the only way to end it was by shutting down the VM.
Relevant log output
and this is podman-desktop logs