I was trying to run hyperion-buildall.sh --auto --verbose in a docker container based

Patrick, Thanks.. The good news is that the run

Thanks Bill, appreciate it. <a h

Latest commit, <a class="commit-link" data-hovercard-type="commit" data-hovercard-url=

Thanks.. The good news is that the run through and the executable

Error running hercules helper in Docker container based on ubuntu:latest about hercules-helper HOT 12 CLOSED

wrljet commented on August 23, 2024

Error running hercules helper in Docker container based on ubuntu:latest

from hercules-helper.

Comments (12)

wrljet commented on August 23, 2024 1

Patrick,

Thanks.. The good news is that the script run through and the executables were created. Just need to sort out one odd thing though: I can start binaries like dasdinit, etc. but when I try to start hercules I get ‘operation not permitted’. After manually executing a sudo chown hercules:hercules hercules the issue is gone. Is this something that has to do with the script? Patrick Raths 華樂善

I made up a Dockerfile myself and reproduced your symptoms.

Adding the --cap-add=sys_nice option to the docker run command fixes it:

docker run -it --rm --cap-add=sys_nice ...

Bill

from hercules-helper.

wrljet commented on August 23, 2024

Patrick,

That's a problem with the Regina REXX configure. REXX is used at the end of the Hercules build process to run tests.
I'll work up a patch and post it.

Bill

from hercules-helper.

patrickraths commented on August 23, 2024

Thanks Bill, appreciate it.

…

On 17 Apr 2023, at 22:12, Bill Lewis ***@***.***> wrote: Patrick, That's a problem with the Regina REXX configure. REXX is used at the end of the Hercules build process to run tests. I'll work up a patch and post it. Bill — Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKNIEAAW2SVKZW6OHAVQKZTXBVFT7ANCNFSM6AAAAAAXAW4DPY>. You are receiving this because you authored the thread.

from hercules-helper.

wrljet commented on August 23, 2024

Latest commit, edae2cb, hopefully will get you going. (at least to the next problem)

Bill

from hercules-helper.

patrickraths commented on August 23, 2024

Thanks.. The good news is that the script run through and the executables were created. Just need to sort out one odd thing though: I can start binaries like dasdinit, etc. but when I try to start hercules I get ‘operation not permitted’. After manually executing a sudo `chown hercules:hercules hercules` the issue is gone. Is this something that has to do with the script? Patrick Raths 華樂善

…

On 17 Apr 2023, at 22:46, Bill Lewis ***@***.***> wrote: Latest commit, edae2cb <edae2cb>, hopefully will get you going. (at least to the next problem) Bill — Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKNIEAC4GNMZB4JWGVX4QVDXBVJUFANCNFSM6AAAAAAXAW4DPY>. You are receiving this because you authored the thread.

from hercules-helper.

wrljet commented on August 23, 2024

I've not seen that happen before.

What was the owner:group of hercules before you modified it?

Can you send me your hyperion-buildall-2023... log. I might see something in there.

If you sent me your Dockerfile would I be able to recreate your setup on a Raspberry Pi (since it's Arm)?

Bill

from hercules-helper.

patrickraths commented on August 23, 2024

Hi Bill, The user/group is hercules:hercules which is being added to the container as part of the build process. Here’s the log file as you requested For docker, here’s the dockerfile I’ve been using. On line 33 of the dockerfile I’m copying a file called hercules into /etc/sudoers.d in order to grant Hercules sudo permission on all commands. I also attached the file here. It’s midnight now here in Hong Kong, time for me to call it a day. Thanks for your help, much appreciated Patrick Raths 華樂善

…

On 17 Apr 2023, at 23:44, Bill Lewis ***@***.***> wrote: I've not seen that happen before. What was the owner:group of hercules before you modified it? Can you send me your hyperion-buildall log. I might see something in there. If you sent me your Dockerfile would I be able to recreate your setup on a Raspberry Pi (since it's Arm)? Bill — Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKNIEAAPTRAFEY4XZF6HWD3XBVQNHANCNFSM6AAAAAAXAW4DPY>. You are receiving this because you authored the thread.

from hercules-helper.

patrickraths commented on August 23, 2024

Btw, this is my “old” Dockerfile that I used to build Hercules 4.x This prepares the environment to build hercules and then I’m executing a script to build Hercules that follows the steps that the official README guides through. The only speciality here is that I compile the external packages for arch64 using these config files upfront and then link them using a corresponding option in the ./configure script This will install the binaries into /opt/hercules and I can execute Hercules with no problem. As you can see from the dockfile I’m pretty much using the same approach in terms of creating user hercules, and then do the compile under hercules. Patrick Raths 華樂善

Begin forwarded message: From: Patrick Raths ***@***.***> Subject: Re: [wrljet/hercules-helper] Error running hercules helper in Docker container based on ubuntu:latest (Issue #34) Date: 18 April 2023 at 00:00:35 HKT To: wrljet/hercules-helper ***@***.***> Cc: wrljet/hercules-helper ***@***.***>, Author ***@***.***> Hi Bill, The user/group is hercules:hercules which is being added to the container as part of the build process. Here’s the log file as you requested

For docker, here’s the dockerfile I’ve been using. On line 33 of the dockerfile I’m copying a file called hercules into /etc/sudoers.d in order to grant Hercules sudo permission on all commands. I also attached the file here.

…

from hercules-helper.

patrickraths commented on August 23, 2024

Just forgot to mention. I’m using the main branch of sdl-hercules-390, i.e. Version 4.5 while I saw that you were using the development brach as the version number was listed with 4.6 when I compiled with your script. Patrick Raths 華樂善

Begin forwarded message: From: Patrick Raths ***@***.***> Subject: Fwd: [wrljet/hercules-helper] Error running hercules helper in Docker container based on ubuntu:latest (Issue #34) Date: 18 April 2023 at 00:20:28 HKT To: wrljet/hercules-helper ***@***.***> Cc: wrljet/hercules-helper ***@***.***>, Author ***@***.***> Btw, this is my “old” Dockerfile that I used to build Hercules 4.x

This prepares the environment to build hercules and then I’m executing a script to build Hercules that follows the steps that the official README guides through. The only speciality here is that I compile the external packages for arch64 using these config files upfront and then link them using a corresponding option in the ./configure script

This will install the binaries into /opt/hercules and I can execute Hercules with no problem. As you can see from the dockfile I’m pretty much using the same approach in terms of creating user hercules, and then do the compile under hercules. Patrick Raths 華樂善 > Begin forwarded message: > > From: Patrick Raths ***@***.***> > Subject: Re: [wrljet/hercules-helper] Error running hercules helper in Docker container based on ubuntu:latest (Issue #34) > Date: 18 April 2023 at 00:00:35 HKT > To: wrljet/hercules-helper ***@***.***> > Cc: wrljet/hercules-helper ***@***.***>, Author ***@***.***> > > Hi Bill, > > The user/group is hercules:hercules which is being added to the container as part of the build process. > > Here’s the log file as you requested

> > For docker, here’s the dockerfile I’ve been using. On line 33 of the dockerfile I’m copying a file called hercules into /etc/sudoers.d in order to grant Hercules sudo permission on all commands. I also attached the file here. > >

> > > It’s midnight now here in Hong Kong, time for me to call it a day. Thanks for your help, much appreciated > > Patrick Raths 華樂善 > >> On 17 Apr 2023, at 23:44, Bill Lewis ***@***.***> wrote: >> >> >> I've not seen that happen before. >> >> What was the owner:group of hercules before you modified it? >> >> Can you send me your hyperion-buildall log. I might see something in there. >> >> If you sent me your Dockerfile would I be able to recreate your setup on a Raspberry Pi (since it's Arm)? >> >> Bill >> >> — >> Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKNIEAAPTRAFEY4XZF6HWD3XBVQNHANCNFSM6AAAAAAXAW4DPY>. >> You are receiving this because you authored the thread. >> > Begin forwarded message: From: Patrick Raths ***@***.***> Subject: Re: [wrljet/hercules-helper] Error running hercules helper in Docker container based on ubuntu:latest (Issue #34) Date: 18 April 2023 at 00:00:35 HKT To: wrljet/hercules-helper ***@***.***> Cc: wrljet/hercules-helper ***@***.***>, Author ***@***.***> Hi Bill, The user/group is hercules:hercules which is being added to the container as part of the build process. Here’s the log file as you requested

…

It’s midnight now here in Hong Kong, time for me to call it a day. Thanks for your help, much appreciated Patrick Raths 華樂善 > On 17 Apr 2023, at 23:44, Bill Lewis ***@***.***> wrote: > > > I've not seen that happen before. > > What was the owner:group of hercules before you modified it? > > Can you send me your hyperion-buildall log. I might see something in there. > > If you sent me your Dockerfile would I be able to recreate your setup on a Raspberry Pi (since it's Arm)? > > Bill > > — > Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKNIEAAPTRAFEY4XZF6HWD3XBVQNHANCNFSM6AAAAAAXAW4DPY>. > You are receiving this because you authored the thread. > Begin forwarded message: From: Patrick Raths ***@***.***> Subject: Re: [wrljet/hercules-helper] Error running hercules helper in Docker container based on ubuntu:latest (Issue #34) Date: 17 April 2023 at 23:23:28 HKT To: wrljet/hercules-helper ***@***.***> Cc: wrljet/hercules-helper ***@***.***>, Author ***@***.***> Thanks.. The good news is that the script run through and the executables were created. Just need to sort out one odd thing though: I can start binaries like dasdinit, etc. but when I try to start hercules I get ‘operation not permitted’. After manually executing a sudo `chown hercules:hercules hercules` the issue is gone. Is this something that has to do with the script? Patrick Raths 華樂善 > On 17 Apr 2023, at 22:46, Bill Lewis ***@***.***> wrote: > > > Latest commit, edae2cb <edae2cb>, hopefully will get you going. (at least to the next problem) > > Bill > > — > Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKNIEAC4GNMZB4JWGVX4QVDXBVJUFANCNFSM6AAAAAAXAW4DPY>. > You are receiving this because you authored the thread. > Begin forwarded message: From: Patrick Raths ***@***.***> Subject: Re: [wrljet/hercules-helper] Error running hercules helper in Docker container based on ubuntu:latest (Issue #34) Date: 17 April 2023 at 22:41:30 HKT To: wrljet/hercules-helper ***@***.***> Cc: wrljet/hercules-helper ***@***.***>, Author ***@***.***> Thanks Bill, appreciate it. > On 17 Apr 2023, at 22:12, Bill Lewis ***@***.***> wrote: > > > Patrick, > > That's a problem with the Regina REXX configure. REXX is used at the end of the Hercules build process to run tests. > I'll work up a patch and post it. > > Bill > > — > Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKNIEAAW2SVKZW6OHAVQKZTXBVFT7ANCNFSM6AAAAAAXAW4DPY>. > You are receiving this because you authored the thread. >

from hercules-helper.

wrljet commented on August 23, 2024

Patrick,

GitHub seems to be acting up, and the files don't appear to be attached.

The Quote Reply feature is not working for me, also.

You can email me directly if you'd like. My email address is at the top of the hyperion-buildall.sh script.

Bill

from hercules-helper.

patrickraths commented on August 23, 2024

Thanks for this. I will check it out. Patrick Raths 華樂善

…

On 19 Apr 2023, at 01:48, Bill Lewis ***@***.***> wrote: Patrick, Thanks.. The good news is that the script run through and the executables were created. Just need to sort out one odd thing though: I can start binaries like dasdinit, etc. but when I try to start hercules I get ‘operation not permitted’. After manually executing a sudo chown hercules:hercules hercules the issue is gone. Is this something that has to do with the script? Patrick Raths 華樂善 I made up a Dockerfile myself and reproduced your symptoms. Adding the --cap-add=sys_nice option to the docker run command fixes it: docker run -it --rm --cap-add=sys_nice ... Bill — Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKNIEAE2SMUHKZPWT7VGXTDXB3HYTANCNFSM6AAAAAAXAW4DPY>. You are receiving this because you authored the thread.

from hercules-helper.

patrickraths commented on August 23, 2024

After adding --cap-add=sys_nice the error no longer appears. However, when running the image on macOS using Docker Desktop there will be warning by hercules that setting the thread priority failed. This is, after confirmation by Docker support, a bug in the Docker Desktop.

from hercules-helper.

Error running hercules helper in Docker container based on ubuntu:latest about hercules-helper HOT 12 CLOSED

Comments (12)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent