Error running build.sh

[Ankur Sinha]

Hello,

I'm running into errors while running ./build.sh in the council-docs
repository for this PR:
https://pagure.io/Fedora-Council/council-docs/pull-request/63

Initially, I got:

>   $ ./build.sh
>
>   This build script is using Podman to run the build in an isolated environment.
>
>   WARN[0000] Error initializing configured OCI runtime runc: no valid executable found for
> OCI runtime runc: invalid argument
>   Error: could not get runtime: default OCI runtime "runc" not found: invalid
> argument 
@hhlp pointed out that it's listed in F31 common bugs here:
https://fedoraproject.org/wiki/Common_F31_bugs#Podman_fails_to_run_contai...

The fix, unfortunately, doesn't seem to work fully:

>   (ins)[asinha@ankur-pc  fedora-council-docs(fedora-join=)]$ rm
> ~/.config/containers/libpod.conf -f
>
>   (ins)[asinha@ankur-pc  fedora-council-docs(fedora-join=)]$ ./build.sh
>
>   This build script is using Podman to run the build in an isolated environment.
>
>   2019-09-25T10:28:24.000811303Z: cannot rm state directory
> '/run/user/1000/crun/42c03e3c10e7b2de25b41fbd1d69ee7fb2ac656a18b77a005e7c6e9556e07195':
> Directory not empty
>   ERRO[0002] Error removing container
> 42c03e3c10e7b2de25b41fbd1d69ee7fb2ac656a18b77a005e7c6e9556e07195: error cleaning up
> container 42c03e3c10e7b2de25b41fbd1d69ee7fb2ac656a18b77a005e7c6e9556e07195: error removing
> container 42c03e3c10e7b2de25b41fbd1d69ee7fb2ac656a18b77a005e7c6e9556e07195 from runtime:
> `/usr/bin/crun delete --force
> 42c03e3c10e7b2de25b41fbd1d69ee7fb2ac656a18b77a005e7c6e9556e07195` failed: exit status 1
>   (ins)[asinha@ankur-pc  fedora-council-docs(fedora-join=)]$
>  
Would anyone have a workaround/fix please?

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London

[Ankur Sinha]

On Wed, Sep 25, 2019 11:36:10 +0100, Ankur Sinha wrote:
>  Hello, 
Weirdly enough on a different system, I get a different error:

>   $ ./build.sh
>
>   This build script is using Podman to run the build in an isolated environment.
>
>   Trying to pull docker.io/antora/antora...
>   Getting image source signatures
>   Copying blob 56174ae7ed1d done
>   Copying blob 284842a36c0d done
>   Copying blob e7c96db7181b done
>   Copying blob 7fa322d31adf done
>   Copying blob ee3fdb6b9c98 done
>   Copying blob 50958466d97a done
>   Copying blob 6fd7bef320a5 done
>   Copying config 8e549fc7fa done
>   Writing manifest to image destination
>   Storing signatures
>   Error processing tar file(exit status 1): there might not be enough IDs available in the
> namespace (requested 0:42 for /etc/shadow): lchown /etc/shadow: invalid argument
>   Error: unable to pull docker.io/antora/antora: unable to pull image: Error committing
> the finished image: error adding layer with blob
> "sha256:e7c96db7181be991f19a9fb6975cdbbd73c65f4a2681348e63a141a2192a5f10": Error
> processing tar file(exit status 1): there might not be enough IDs available in the
> namespace (requested 0:42 for /etc/shadow): lchown /etc/shadow: invalid argument 
I think this has been discussed here, but I don't know enough about
podman to try any of it out.
https://www.redhat.com/sysadmin/rootless-podman

One would expect it to "work out of the box". If no one else has seen
these and we aren't aware of any solutions, I'll go file bugs.

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London

[Ben Cotton]

I assume from the F31 commonbugs link that you're using F31? It builds
fine for me on F30, so that's the most help I can offer.

--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis

[Ankur Sinha]

On Wed, Sep 25, 2019 09:39:27 -0400, Ben Cotton wrote:
>  I assume from the F31 commonbugs link that you're using F31? It
> builds
>  fine for me on F30, so that's the most help I can offer. 
Yes, both all my systems are F31 now :)

I've e-mailed the QA list too. Hopefully they'll know what's up. I'll
keep everyone posted.

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London

[Ankur Sinha]

On Wed, Sep 25, 2019 15:12:33 +0100, Ankur Sinha wrote:
>  On Wed, Sep 25, 2019 09:39:27 -0400, Ben Cotton wrote:
>  > I assume from the F31 commonbugs link that you're using F31? It builds
>  > fine for me on F30, so that's the most help I can offer.
>   
I filed a bug against podman now:
https://bugzilla.redhat.com/show_bug.cgi?id=1756059

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London

[Ankur Sinha]

On Thu, Sep 26, 2019 17:46:38 +0100, Ankur Sinha wrote:
>  On Wed, Sep 25, 2019 15:12:33 +0100, Ankur Sinha wrote:
>  > On Wed, Sep 25, 2019 09:39:27 -0400, Ben Cotton wrote:
>  > > I assume from the F31 commonbugs link that you're using F31? It builds
>  > > fine for me on F30, so that's the most help I can offer.
>  > 
>  
>  I filed a bug against podman now:
>  https://bugzilla.redhat.com/show_bug.cgi?id=1756059 
This seems to be solved. One must ensure that NOTIFY_SOCKET is not set.
This was set in GNOME previously and is now fixed (I think).

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) |
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London