Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1888681 - dnf not working inside of armhfp containers
Summary: dnf not working inside of armhfp containers
Status: CLOSED DUPLICATE of bug 1887445
Alias: None
Product: Fedora
Classification: Fedora
Component: buildah
Version: 33
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Lokesh Mandvekar
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
Reported: 2020-10-15 13:36 UTC by Dennis Gilmore
Modified: 2020-10-15 17:10 UTC (History)
22 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-10-15 17:10:53 UTC
Type: Bug

Attachments (Terms of Use)

Description Dennis Gilmore 2020-10-15 13:36:45 UTC
Description of problem:

[dennis@korolev coursera-dl]$ buildah bud Dockerfile.f33 tag coursera-dl
STEP 1: FROM fedora:33
Getting image source signatures
Copying blob 363c3f551196 done  
Copying config 99725236e6 done  
Writing manifest to image destination
Storing signatures
STEP 2: LABEL maintainer ""
STEP 3: RUN dnf -y update &&     dnf install gcc gcc-c++ openssl-devel python3-devel &&     dnf clean all
Fatal Python error: init_interp_main: can't initialize time
Python runtime state: core initialized
PermissionError: [Errno 1] Operation not permitted

Current thread 0xb6efe010 (most recent call first):
<no Python frame>
error building at STEP "RUN dnf -y update &&     dnf install gcc gcc-c++ openssl-devel python3-devel &&     dnf clean all": error while running runtime: exit status 1
ERRO exit status 1                                
[dennis@korolev coursera-dl]$

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. run buildah on 32 bit arm machine and attempt to run dnf

Actual results:

Expected results:

Additional info:

Comment 1 Paul Whalen 2020-10-15 14:12:23 UTC
I ran the dnf command manually in the container:

(30/35): libnfnetlink-1.0.1-18.fc33.armv7hl.rpm 256 kB/s |  28 kB     00:00    
(31/35): httpd-2.4.46-1.fc33.armv7hl.rpm        1.5 MB/s | 1.3 MB     00:00    
(32/35): mailcap-2.1.49-2.fc33.noarch.rpm       257 kB/s |  33 kB     00:00    
(33/35): libseccomp-2.5.0-3.fc33.armv7hl.rpm    382 kB/s |  74 kB     00:00    
(34/35): qrencode-libs-4.0.2-6.fc33.armv7hl.rpm 335 kB/s |  57 kB     00:00    
(35/35): xkeyboard-config-2.30-3.fc33.noarch.rp 1.1 MB/s | 749 kB     00:00    
Total                                           2.7 MB/s | 9.7 MB     00:03     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                        1/1 
  Installing       : xkeyboard-config-2.30-3.fc33.noarch                   1/35 
Error unpacking rpm package xkeyboard-config-2.30-3.fc33.noarch
  Installing       : mailcap-2.1.49-2.fc33.noarch                          2/35 
error: unpacking of archive failed on file /usr/share/X11/xkb/compat/README;5f88569a: cpio: utime
error: xkeyboard-config-2.30-3.fc33.noarch: install failed

Error unpacking rpm package mailcap-2.1.49-2.fc33.noarch
  Running scriptlet: httpd-filesystem-2.4.46-1.fc33.noarch                 3/35 
error: unpacking of archive failed on file /etc/mailcap;5f88569a: cpio: utime
error: mailcap-2.1.49-2.fc33.noarch: install failed

  Installing       : httpd-filesystem-2.4.46-1.fc33.noarch                 3/35 
Error unpacking rpm package httpd-filesystem-2.4.46-1.fc33.noarch
  Installing       : fedora-logos-httpd-30.0.2-5.fc33.noarch               4/35 
error: unpacking of archive failed on file /etc/httpd/conf.d/README;5f88569a: cpio: utime
error: httpd-filesystem-2.4.46-1.fc33.noarch: install failed

Comment 2 Miro Hrončok 2020-10-15 17:10:53 UTC

*** This bug has been marked as a duplicate of bug 1887445 ***

Note You need to log in before you can comment on or make changes to this bug.