podman: osx can't build due to no space left on device
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
g-extensions-3.7.4.3 urllib3-1.26.7 wrapt-1.12.1 zipp-3.5.0 WARNING: Running pip as the ‘root’ user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv Error: error committing container for step {Env:[PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin LANG=C.UTF-8 GPG_KEY=0D96DF4D4110E5C43FBFB17F2D347EA6AA65421D PYTHON_VERSION=3.7.12 PYTHON_PIP_VERSION=21.2.4 PYTHON_SETUPTOOLS_VERSION=57.5.0 PYTHON_GET_PIP_URL=https://github.com/pypa/get-pip/raw/c20b0cfd643cd4a19246ccf204e2997af70f6b21/public/get-pip.py PYTHON_GET_PIP_SHA256=fa6f3fb93cce234cd4e8dd2beb54a51ab9c247653b52855a48dd44e6b21ff28b] Command:run Args:[pip install -r requirements.txt] Flags:[] Attrs:map[] Message:RUN pip install -r requirements.txt Original:RUN pip install -r requirements.txt}: error copying layers and metadata for container “80ffc4528da65d5f2c7ef516711fe94b0be9908a65b9386cfcdc1c95a56a3368”: writing blob: adding layer with blob “sha256:9e9e4dd78a45a27380d9df62bd5187c9d094a636c2c7d97dbc2a3829bda71df0”: Error processing tar file(exit status 1): open /usr/local/lib/python3.7/site-packages/tensorflow/python/training/checkpoint_state_pb2.py: no space left on device
Steps to reproduce the issue:
- Dockerfile
FROM python:3.7-slim
COPY . /app
WORKDIR /app
RUN pip install -r requirements.txt
- requirements.txt
seldon-core==1.6.0
tensorflow
Pillow
- podman build . -t myname
Describe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
Client:
Version: 3.3.1
API Version: 3.3.1
Go Version: go1.17
Built: Tue Aug 31 03:15:26 2021
OS/Arch: darwin/amd64
Server:
Version: 3.3.1
API Version: 3.3.1
Go Version: go1.16.6
Built: Tue Aug 31 04:46:36 2021
OS/Arch: linux/amd64
Output of podman info --debug:
host:
arch: amd64
buildahVersion: 1.22.3
cgroupControllers: []
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: conmon-2.0.29-2.fc34.x86_64
path: /usr/bin/conmon
version: 'conmon version 2.0.29, commit: '
cpus: 1
distribution:
distribution: fedora
version: "34"
eventLogger: journald
hostname: localhost
idMappings:
gidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
uidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
kernel: 5.13.16-200.fc34.x86_64
linkmode: dynamic
memFree: 1700859904
memTotal: 2061852672
ociRuntime:
name: crun
package: crun-1.0-1.fc34.x86_64
path: /usr/bin/crun
version: |-
crun version 1.0
commit: 139dc6971e2f1d931af520188763e984d6cdfbf8
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
os: linux
remoteSocket:
exists: true
path: /run/user/1000/podman/podman.sock
security:
apparmorEnabled: false
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: true
seccompEnabled: true
seccompProfilePath: /usr/share/containers/seccomp.json
selinuxEnabled: true
serviceIsRemote: true
slirp4netns:
executable: /usr/bin/slirp4netns
package: slirp4netns-1.1.12-2.fc34.x86_64
version: |-
slirp4netns version 1.1.12
commit: 7a104a101aa3278a2152351a082a6df71f57c9a3
libslirp: 4.4.0
SLIRP_CONFIG_VERSION_MAX: 3
libseccomp: 2.5.0
swapFree: 0
swapTotal: 0
uptime: 20m 4.01s
registries:
search:
- registry.fedoraproject.org
- registry.access.redhat.com
- docker.io
- quay.io
store:
configFile: /var/home/core/.config/containers/storage.conf
containerStore:
number: 0
paused: 0
running: 0
stopped: 0
graphDriverName: overlay
graphOptions: {}
graphRoot: /var/home/core/.local/share/containers/storage
graphStatus:
Backing Filesystem: xfs
Native Overlay Diff: "true"
Supports d_type: "true"
Using metacopy: "false"
imageStore:
number: 3
runRoot: /run/user/1000/containers
volumePath: /var/home/core/.local/share/containers/storage/volumes
version:
APIVersion: 3.3.1
Built: 1630356396
BuiltTime: Mon Aug 30 20:46:36 2021
GitCommit: ""
GoVersion: go1.16.6
OsArch: linux/amd64
Version: 3.3.1
Package info (e.g. output of rpm -q podman or apt list podman):
(paste your output here)
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes/No
Additional environment details (AWS, VirtualBox, physical, etc.):
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 38 (34 by maintainers)
Commits related to this issue
- increase default machine vm size to 20 Context: containers/podman/issues/11712 Signed-off-by: Valentin Rothberg <rothberg@redhat.com> — committed to vrothberg/common by vrothberg 3 years ago
- increase default machine vm size to 100GiB Context: containers/podman/issues/11712 Signed-off-by: Valentin Rothberg <rothberg@redhat.com> — committed to vrothberg/common by vrothberg 3 years ago
I think the default should be 20GB and be configurable. I just got a new laptop that defaults to 1TB sdd.
podman machine listalready gives the info, but I want that info inpodman infoas well. That’s what we request in issue and BZs and having data on (running) machines can help speed things up.@ashley-cui knock that out and we can review it as part of the regular review process. thanks
helper_binariesis general, we will need this for other podman binaries. Other than that an extra[machine]section for the fields SGTM.