* [ISSUE] Docker environment to build and test new packages
@ 2022-02-04 18:02 erezgeva
2022-02-04 18:07 ` Chocimier
` (23 more replies)
0 siblings, 24 replies; 25+ messages in thread
From: erezgeva @ 2022-02-04 18:02 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
New issue by erezgeva on void-packages repository
https://github.com/void-linux/void-packages/issues/35410
Description:
Hi,
I work on a new library.
And I wish to write a template for my new library and test in on a void Linux system.
That is to compile and package it.
My goal is to provide the template file so any user that wishes to package the new library, can use the template, for this propose.
My problem is that I can not manage to set such an environment.
In order to test and build I must compile the void-packages bootstrap.
This process take few hours and always fail on the GCC compilation.
Why wouldn't you provide a Docker image with the void-packages bootstrap already built. So we can simply write our package template file and test it.
Later other users and the void-Linux contributors can simply use it.
Thanks
Erez
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
@ 2022-02-04 18:07 ` Chocimier
2022-03-26 18:23 ` [ISSUE] [CLOSED] " Chocimier
` (22 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: Chocimier @ 2022-02-04 18:07 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 169 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1030227977
Comment:
Use `binary-bootstrap`.
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: [ISSUE] [CLOSED] Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
2022-02-04 18:07 ` Chocimier
@ 2022-03-26 18:23 ` Chocimier
2022-03-29 1:53 ` erezgeva
` (21 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: Chocimier @ 2022-03-26 18:23 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
Closed issue by erezgeva on void-packages repository
https://github.com/void-linux/void-packages/issues/35410
Description:
Hi,
I work on a new library.
And I wish to write a template for my new library and test in on a void Linux system.
That is to compile and package it.
My goal is to provide the template file so any user that wishes to package the new library, can use the template, for this propose.
My problem is that I can not manage to set such an environment.
In order to test and build I must compile the void-packages bootstrap.
This process take few hours and always fail on the GCC compilation.
Why wouldn't you provide a Docker image with the void-packages bootstrap already built. So we can simply write our package template file and test it.
Later other users and the void-Linux contributors can simply use it.
Thanks
Erez
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
2022-02-04 18:07 ` Chocimier
2022-03-26 18:23 ` [ISSUE] [CLOSED] " Chocimier
@ 2022-03-29 1:53 ` erezgeva
2022-03-29 2:06 ` Duncaen
` (20 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: erezgeva @ 2022-03-29 1:53 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 162 bytes --]
New comment by erezgeva on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1081317854
Comment:
Links? Documents?
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (2 preceding siblings ...)
2022-03-29 1:53 ` erezgeva
@ 2022-03-29 2:06 ` Duncaen
2022-03-29 9:13 ` erezgeva
` (19 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: Duncaen @ 2022-03-29 2:06 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1081323603
Comment:
> Why wouldn't you provide a Docker image with the void-packages bootstrap already built. So we can simply write our package template file and test it.
We already provide a repository with the packages build.
By doing `./xbps-src binary-boostrap` instead of `./xbps-src bootstrap` you don't have to build anything.
https://github.com/void-linux/void-packages#quick-start
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (3 preceding siblings ...)
2022-03-29 2:06 ` Duncaen
@ 2022-03-29 9:13 ` erezgeva
2022-03-29 12:33 ` erezgeva
` (18 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: erezgeva @ 2022-03-29 9:13 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 151 bytes --]
New comment by erezgeva on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1081625964
Comment:
Thanks
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (4 preceding siblings ...)
2022-03-29 9:13 ` erezgeva
@ 2022-03-29 12:33 ` erezgeva
2022-03-29 17:40 ` Chocimier
` (17 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: erezgeva @ 2022-03-29 12:33 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
New comment by erezgeva on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1081814504
Comment:
You use namespaces and 'prctl - operations on a process or thread'
And you ask not to use 'root'.
All of this overhead make the build impossible to work in docker.
I understand why adding them, but make them mandatory make the task very hard to accomplish.
And I will not install a system that I can not check on Docker or Virtual machine first.
Nor will I recommend it.
Speed is important, but a distribution need to be flexible and work on different environments.
And no, building packages should be simple and **NOT** bump with
`ERROR unshare (Operation not permitted)`
And
`ERROR: prctl SECBIT_NOROOT (Operation not permitted)`
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (5 preceding siblings ...)
2022-03-29 12:33 ` erezgeva
@ 2022-03-29 17:40 ` Chocimier
2022-03-31 13:25 ` erezgeva
` (16 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: Chocimier @ 2022-03-29 17:40 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 286 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1082183500
Comment:
In VMs Void works perfectly fine. For using xbps-src in a foreign Linux distribution or in docker refer to documentation linked previously.
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (6 preceding siblings ...)
2022-03-29 17:40 ` Chocimier
@ 2022-03-31 13:25 ` erezgeva
2022-03-31 13:28 ` erezgeva
` (15 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: erezgeva @ 2022-03-31 13:25 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
New comment by erezgeva on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1084574258
Comment:
Look on the https://github.com/void-linux/void-packages#chroot-methods
- xbps-uunshare(1) (default)
- xbps-uchroot(1)
- bwrap(1) link to another site.
As for foreign, it is nice.
But I need to use container like docker.
The reason is that I can later use continuous integration on a GIT based server.
That create all relevant packages, for testing or for distribution.
However I can not create void using xbps-src.
xbps-src should works in a container same as dpkg-buildpackage, rpmbuild and archlinux makepkg.
No namespaces, no root user, no prctl, and no setgid.
And no third parties tools, please.
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (7 preceding siblings ...)
2022-03-31 13:25 ` erezgeva
@ 2022-03-31 13:28 ` erezgeva
2022-03-31 14:27 ` Duncaen
` (14 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: erezgeva @ 2022-03-31 13:28 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 305 bytes --]
New comment by erezgeva on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1084577662
Comment:
One of my first lessons as software engineers on software is.
Make it simple, make it safe.
Provide the advanced options for advanced users, not the opposite.
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (8 preceding siblings ...)
2022-03-31 13:28 ` erezgeva
@ 2022-03-31 14:27 ` Duncaen
2022-03-31 15:36 ` erezgeva
` (13 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: Duncaen @ 2022-03-31 14:27 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1084662772
Comment:
Its simply not how xbps-src works, the core idea is that builds happen in clean and reproducible environments and not on the host system.
If you really want to build packages using xbps-src in docker without allowing nested namespaces and uid maps, check how the github CI is setup, by creating temporary containers containing the build environment and invoke xbps-src in a way that it allows to use the container as build environment.
https://github.com/void-linux/void-packages/blob/master/.github/workflows/build.yaml
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (9 preceding siblings ...)
2022-03-31 14:27 ` Duncaen
@ 2022-03-31 15:36 ` erezgeva
2022-03-31 19:47 ` Anachron
` (12 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: erezgeva @ 2022-03-31 15:36 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
New comment by erezgeva on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1084757177
Comment:
I do not want to build on the host system.
Docker container are the best clean and reproducible environments there is.
The link you send looks interesting.
It run
https://github.com/void-linux/void-packages/blob/master/common/travis/build.sh
It does not seems to have options to disable unshare or uchroot.
But looks like something in the environment is different.
Is it possible to use this Docker?
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (10 preceding siblings ...)
2022-03-31 15:36 ` erezgeva
@ 2022-03-31 19:47 ` Anachron
2022-03-31 21:44 ` erezgeva
` (11 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: Anachron @ 2022-03-31 19:47 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
New comment by Anachron on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1085031066
Comment:
Just create a script to prepare the build env inside the docker container on start.
You can create a non-root user, clone void-packages and run binary-bootstrap.
Then create /tmp/bootstrapped (or alike) so you know when its finished and run your builds inside.
(Of course, if you make a persistant container you gotta pull from remote origin).
Maybe I'm missing the point here?
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (11 preceding siblings ...)
2022-03-31 19:47 ` Anachron
@ 2022-03-31 21:44 ` erezgeva
2022-03-31 22:50 ` paper42
` (10 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: erezgeva @ 2022-03-31 21:44 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
New comment by erezgeva on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1085153375
Comment:
This is what I do.
Yet when I run
`./xbps-src pkg`
I get errors on namespace.
I do not understand. Are there different xbps-src applications?
Is there a configuration that cause the xbps-src to use xbps-uunshare/xbps-uchroot or skip them.
Why don't their is a simple instructions / a docker container that I can use and build my package.
I yet do not receive an answerer.
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (12 preceding siblings ...)
2022-03-31 21:44 ` erezgeva
@ 2022-03-31 22:50 ` paper42
2022-04-01 4:31 ` Anachron
` (9 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: paper42 @ 2022-03-31 22:50 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1085207003
Comment:
> Yet when I run
> ./xbps-src pkg
> I get errors on namespace.
xbps-src creates a directory with a minimal void system, the state of this system is defined (more or less) by HEAD. The package is then built in this "container" which uses namespaces, so you can't run that nested inside another container without taking extra steps (if that's possible).
Alternatively, you can use the ethereal chroot style which uses symlinks to emulate a chroot without actually changing the root, but this destroys the container. For documentation on this, see common/chroot-style/ethereal.sh and the way CI is set up that was already linked before.
@Anachron missed the point of this issue, please ignore that comment
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (13 preceding siblings ...)
2022-03-31 22:50 ` paper42
@ 2022-04-01 4:31 ` Anachron
2022-04-01 4:38 ` Anachron
` (8 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: Anachron @ 2022-04-01 4:31 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 419 bytes --]
New comment by Anachron on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1085410594
Comment:
Indeed I was confused but I get it now. The problem is we chroot to build cleanly, but this takes extra permissions inside the container.
So maybe we could create another chroot-style which doesnt need it and doesnt destroy the container. I'll see what I can come up with.
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (14 preceding siblings ...)
2022-04-01 4:31 ` Anachron
@ 2022-04-01 4:38 ` Anachron
2022-04-01 8:07 ` erezgeva
` (7 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: Anachron @ 2022-04-01 4:38 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
New comment by Anachron on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1085410594
Comment:
Indeed I was confused but I get it now. The problem is we chroot to build cleanly, but this takes extra permissions inside the container.
So maybe we could create another chroot-style which doesnt need it and doesnt destroy the container. I'll see what I can come up with.
Maybe something like https://github.com/dex4er/fakechroot but there would be quite some things to Patch inside xbps-src chroot setup.
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (15 preceding siblings ...)
2022-04-01 4:38 ` Anachron
@ 2022-04-01 8:07 ` erezgeva
2022-04-01 10:09 ` Duncaen
` (6 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: erezgeva @ 2022-04-01 8:07 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 263 bytes --]
New comment by erezgeva on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1085569343
Comment:
Thanks.
Yes, Debian for example uses fakeroot,
The purpose is to create an archive with files with root permissions.
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (16 preceding siblings ...)
2022-04-01 8:07 ` erezgeva
@ 2022-04-01 10:09 ` Duncaen
2022-04-01 10:55 ` Anachron
` (5 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: Duncaen @ 2022-04-01 10:09 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 246 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1085711327
Comment:
We removed fakeroot support because it was exceptionally broken and resulted in random build failures.
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (17 preceding siblings ...)
2022-04-01 10:09 ` Duncaen
@ 2022-04-01 10:55 ` Anachron
2023-04-27 10:26 ` bruceloco
` (4 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: Anachron @ 2022-04-01 10:55 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 433 bytes --]
New comment by Anachron on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1085756632
Comment:
> We removed fakeroot support because it was exceptionally broken and resulted in random build failures.
That was in 2014, no? https://github.com/void-linux/void-packages/commit/d75238b0d807302344f5ed7df2b9aa541cae3544
Or did we try `fakeroot` again after that but still had issues?
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (18 preceding siblings ...)
2022-04-01 10:55 ` Anachron
@ 2023-04-27 10:26 ` bruceloco
2023-04-27 11:21 ` classabbyamp
` (3 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: bruceloco @ 2023-04-27 10:26 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
New comment by bruceloco on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1525405659
Comment:
What about chroot?
I have a debian install on the target - chromebook arm64
create urandom nodes that map to debian /dev/urandom(otherwise git fails)
chroot into the void install
created a user which i added to the xbuilder group
./xbps-src bootstrap gives me
ERROR unshare (Operation not permitted)
I don't even know if this is an error or just some leftover hang from some irrelevant check
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (19 preceding siblings ...)
2023-04-27 10:26 ` bruceloco
@ 2023-04-27 11:21 ` classabbyamp
2023-04-27 13:11 ` bruceloco
` (2 subsequent siblings)
23 siblings, 0 replies; 25+ messages in thread
From: classabbyamp @ 2023-04-27 11:21 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1525516053
Comment:
see the readme, you can run xbps-src on debian directly, because the build environment is a chroot/container already:
> If `xbps-uunshare` does not work because of lack of `user_namespaces(7)` support, try other [chroot methods](https://github.com/void-linux/void-packages#chroot-methods).
https://github.com/void-linux/void-packages#foreign
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (20 preceding siblings ...)
2023-04-27 11:21 ` classabbyamp
@ 2023-04-27 13:11 ` bruceloco
2023-04-27 13:45 ` bruceloco
2023-04-27 18:49 ` bruceloco
23 siblings, 0 replies; 25+ messages in thread
From: bruceloco @ 2023-04-27 13:11 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
New comment by bruceloco on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1525673378
Comment:
> see the readme, you can run xbps-src on debian directly, because the build environment is a chroot/container already:
>
> > If `xbps-uunshare` does not work because of lack of `user_namespaces(7)` support, try other [chroot methods](https://github.com/void-linux/void-packages#chroot-methods).
>
> https://github.com/void-linux/void-packages#foreign
Yeah, i followed that, the CHROOT is now fine
except now i get the prctl SECBIT_NOROOT (Operation not permitted)
example
./xpbs-src pkg linux6.2
ERROR: prctl SECBIT_NOROOT (Operation not permitted)
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (21 preceding siblings ...)
2023-04-27 13:11 ` bruceloco
@ 2023-04-27 13:45 ` bruceloco
2023-04-27 18:49 ` bruceloco
23 siblings, 0 replies; 25+ messages in thread
From: bruceloco @ 2023-04-27 13:45 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 902 bytes --]
New comment by bruceloco on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1525673378
Comment:
> see the readme, you can run xbps-src on debian directly, because the build environment is a chroot/container already:
>
> > If `xbps-uunshare` does not work because of lack of `user_namespaces(7)` support, try other [chroot methods](https://github.com/void-linux/void-packages#chroot-methods).
>
> https://github.com/void-linux/void-packages#foreign
Yeah, i followed that, the CHROOT is now fine
except now i get the prctl SECBIT_NOROOT (Operation not permitted)
example
./xpbs-src pkg linux6.2
ERROR: prctl SECBIT_NOROOT (Operation not permitted)
What does this mean? does this mean that the chroot has this option?
my pid has all capabilities, output of getpcaps =ep
or is this a process inside the chroot which is a void process?
^ permalink raw reply [flat|nested] 25+ messages in thread
* Re: Docker environment to build and test new packages
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
` (22 preceding siblings ...)
2023-04-27 13:45 ` bruceloco
@ 2023-04-27 18:49 ` bruceloco
23 siblings, 0 replies; 25+ messages in thread
From: bruceloco @ 2023-04-27 18:49 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
New comment by bruceloco on void-packages repository
https://github.com/void-linux/void-packages/issues/35410#issuecomment-1525673378
Comment:
> see the readme, you can run xbps-src on debian directly, because the build environment is a chroot/container already:
>
> > If `xbps-uunshare` does not work because of lack of `user_namespaces(7)` support, try other [chroot methods](https://github.com/void-linux/void-packages#chroot-methods).
>
> https://github.com/void-linux/void-packages#foreign
Yeah, i followed that, the CHROOT is now fine
except now i get the prctl SECBIT_NOROOT (Operation not permitted)
example
./xpbs-src pkg linux6.2
ERROR: prctl SECBIT_NOROOT (Operation not permitted)
What does this mean? does this mean that the chroot has this option?
my pid has all capabilities, output of getpcaps =ep
or is this a process inside the chroot which is a void process?
I also tired XBPS_ALLOW_CHROOT_BREAKOUT=yes and ran as root
the result was also
ERROR: prctl SECBIT_NOROOT (Operation not permitted)
^ permalink raw reply [flat|nested] 25+ messages in thread
end of thread, other threads:[~2023-04-27 18:49 UTC | newest]
Thread overview: 25+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-04 18:02 [ISSUE] Docker environment to build and test new packages erezgeva
2022-02-04 18:07 ` Chocimier
2022-03-26 18:23 ` [ISSUE] [CLOSED] " Chocimier
2022-03-29 1:53 ` erezgeva
2022-03-29 2:06 ` Duncaen
2022-03-29 9:13 ` erezgeva
2022-03-29 12:33 ` erezgeva
2022-03-29 17:40 ` Chocimier
2022-03-31 13:25 ` erezgeva
2022-03-31 13:28 ` erezgeva
2022-03-31 14:27 ` Duncaen
2022-03-31 15:36 ` erezgeva
2022-03-31 19:47 ` Anachron
2022-03-31 21:44 ` erezgeva
2022-03-31 22:50 ` paper42
2022-04-01 4:31 ` Anachron
2022-04-01 4:38 ` Anachron
2022-04-01 8:07 ` erezgeva
2022-04-01 10:09 ` Duncaen
2022-04-01 10:55 ` Anachron
2023-04-27 10:26 ` bruceloco
2023-04-27 11:21 ` classabbyamp
2023-04-27 13:11 ` bruceloco
2023-04-27 13:45 ` bruceloco
2023-04-27 18:49 ` bruceloco
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).