Closed jianzhangbjz closed 1 week ago
Duplicate of #13967
You best option is to podman machine rm and create a new one or manually delete some files in the VM until podman works again.
There is no /var/home/ folder, I'm unsure why it tried to open it.
Well all these paths are in the VM so you need podman machine ssh
first.
Hi @Luap99 , thanks for your updates! And, it still fails after recreting the machine
, any suggest? Thanks!
jiazha-mac:~ jiazha$ podman machine stop
Machine "podman-machine-default" stopped successfully
jiazha-mac:~ jiazha$ podman machine rm
The following files will be deleted:
/Users/jiazha/.config/containers/podman/machine/applehv/podman-machine-default.json
/var/folders/5n/w9ysf4w93jnfy7k19xxct31c0000gn/T/podman/podman-machine-default.sock
/var/folders/5n/w9ysf4w93jnfy7k19xxct31c0000gn/T/podman/podman-machine-default-gvproxy.sock
/var/folders/5n/w9ysf4w93jnfy7k19xxct31c0000gn/T/podman/podman-machine-default-api.sock
/var/folders/5n/w9ysf4w93jnfy7k19xxct31c0000gn/T/podman/podman-machine-default.log
Are you sure you want to continue? [y/N] y
jiazha-mac:~ jiazha$ podman machine init
Looking up Podman Machine image at quay.io/podman/machine-os:5.0 to create VM
Extracting compressed file: podman-machine-default-arm64.raw: done
Machine init complete
To start your machine run:
podman machine start
jiazha-mac:~ jiazha$ podman machine start
Starting machine "podman-machine-default"
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: /var/run/docker.sock
Docker API clients default to this address. You do not need to set DOCKER_HOST.
Machine "podman-machine-default" started successfully
jiazha-mac:~ jiazha$ podman machine list
NAME VM TYPE CREATED LAST UP CPUS MEMORY DISK SIZE
podman-machine-default* applehv About a minute ago Currently running 5 2GiB 100GiB
jiazha-mac:~ jiazha$ sudo podman build -f catalog.Dockerfile -t quay.io/olmqe/nginx-index:bug31645 .
Password:
Error: failed Request: Unable to copy tar file from request body /v5.0.0/libpod/build?dockerfile=%5B%22catalog.Dockerfile%22%5D&forcerm=1&httpproxy=1&identitylabel=1&idmappingoptions=%7B%22HostUIDMapping%22%3Atrue%2C%22HostGIDMapping%22%3Atrue%2C%22UIDMap%22%3A%5B%5D%2C%22GIDMap%22%3A%5B%5D%2C%22AutoUserNs%22%3Afalse%2C%22AutoUserNsOpts%22%3A%7B%22Size%22%3A0%2C%22InitialSize%22%3A0%2C%22PasswdFile%22%3A%22%22%2C%22GroupFile%22%3A%22%22%2C%22AdditionalUIDMappings%22%3Anull%2C%22AdditionalGIDMappings%22%3Anull%7D%7D&isolation=3&jobs=1&layers=1&networkmode=0&nsoptions=%5B%7B%22Name%22%3A%22user%22%2C%22Host%22%3Atrue%2C%22Path%22%3A%22%22%7D%5D&omithistory=0&output=quay.io%2Folmqe%2Fnginx-index%3Abug31645&outputformat=application%2Fvnd.oci.image.manifest.v1%2Bjson&pullpolicy=missing&rm=1&shmsize=67108864&t=quay.io%2Folmqe%2Fnginx-index%3Abug31645
One more question, how can I specify the space? Thanks!
jiazha-mac:~ jiazha$ podman machine start
Starting machine "podman-machine-default"
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
Error: mkdir /var/lib/containers/storage/overlay/l: no space left on device
/usr/bin/bash: line 10: /etc/systemd/system.conf.d/default-env.conf: No space left on device
WARN[0009] API socket failed ping test
API forwarding listening on: /var/run/docker.sock
Docker API clients default to this address. You do not need to set DOCKER_HOST.
Machine "podman-machine-default" started successfully
Error: failed Request: Unable to copy tar file from request body /v5.0.0/libpod/build?dockerfile=%5B%22catalog.Dockerfile%22%5D&forcerm=1&httpproxy=1&identitylabel=1&idmappingoptions=%7B%22HostUIDMapping%22%3Atrue%2C%22HostGIDMapping%22%3Atrue%2C%22UIDMap%22%3A%5B%5D%2C%22GIDMap%22%3A%5B%5D%2C%22AutoUserNs%22%3Afalse%2C%22AutoUserNsOpts%22%3A%7B%22Size%22%3A0%2C%22InitialSize%22%3A0%2C%22PasswdFile%22%3A%22%22%2C%22GroupFile%22%3A%22%22%2C%22AdditionalUIDMappings%22%3Anull%2C%22AdditionalGIDMappings%22%3Anull%7D%7D&isolation=3&jobs=1&layers=1&networkmode=0&nsoptions=%5B%7B%22Name%22%3A%22user%22%2C%22Host%22%3Atrue%2C%22Path%22%3A%22%22%7D%5D&omithistory=0&output=quay.io%2Folmqe%2Fnginx-index%3Abug31645&outputformat=application%2Fvnd.oci.image.manifest.v1%2Bjson&pullpolicy=missing&rm=1&shmsize=67108864&t=quay.io%2Folmqe%2Fnginx-index%3Abug31645
How large is you build context directory?
The VM size is given with podman machine init --disk-size
, I think 100 (GB) is the default
100G as default.
jiazha-mac:~ jiazha$ podman build -f catalog.Dockerfile -t quay.io/olmqe/nginx-index:bug31645 .
ERRO[0241] 1 error occurred:
* io: read/write on closed pipe
Error: failed Request: Unable to copy tar file from request body /v5.0.0/libpod/build?dockerfile=%5B%22catalog.Dockerfile%22%5D&forcerm=1&httpproxy=1&identitylabel=1&idmappingoptions=%7B%22HostUIDMapping%22%3Atrue%2C%22HostGIDMapping%22%3Atrue%2C%22UIDMap%22%3A%5B%5D%2C%22GIDMap%22%3A%5B%5D%2C%22AutoUserNs%22%3Afalse%2C%22AutoUserNsOpts%22%3A%7B%22Size%22%3A0%2C%22InitialSize%22%3A0%2C%22PasswdFile%22%3A%22%22%2C%22GroupFile%22%3A%22%22%2C%22AdditionalUIDMappings%22%3Anull%2C%22AdditionalGIDMappings%22%3Anull%7D%7D&isolation=3&jobs=1&layers=1&networkmode=0&nsoptions=%5B%7B%22Name%22%3A%22user%22%2C%22Host%22%3Atrue%2C%22Path%22%3A%22%22%7D%5D&omithistory=0&output=quay.io%2Folmqe%2Fnginx-index%3Abug31645&outputformat=application%2Fvnd.oci.image.manifest.v1%2Bjson&pullpolicy=missing&rm=1&shmsize=67108864&t=quay.io%2Folmqe%2Fnginx-index%3Abug31645
jiazha-mac:~ jiazha$ podman machine list
NAME VM TYPE CREATED LAST UP CPUS MEMORY DISK SIZE
podman-machine-default* applehv 5 hours ago Currently running 5 2GiB 100GiB
``
Issue Description
Cannot empty the space.
Steps to reproduce the issue
Steps to reproduce the issue
Describe the results you received
There is no
/var/home/
folder, I'm unsure why it tried to open it.Describe the results you expected
I can remove those images successfully.
podman info output
Podman in a container
No
Privileged Or Rootless
None
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting