Hi Wolf,
Patch is now submitted, see following for details.
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64171
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64173
Now we find out what I forgot. ;-)
Thanks again for your help,
Graham
On Tue, 13 Jun 2023 at 17:56, Graham Addis wrote:
>
> Hi Wo
Hi Wolf,
Well I managed to sort it out last weekend.
I have added a --docker-entry-point option which can be invoked
multiple times to provide the docker EntryPoint value in exec form.
I have left the --entry-point behaviour alone except the
--docker-entry-point takes precedence.
I still have t
Hi Wolf,
Similar to what I was trying, which didn't work. I'll try to have a go
one evening and try and work out where I went wrong.
Thanks again. Graham
On Mon, 5 Jun 2023 at 18:35, wolf wrote:
>
> On 2023-06-05 16:37:50 +0100, Graham Addis wrote:
> > Hi Wolf,
> >
> > Not a particularly succes
On 2023-06-05 16:37:50 +0100, Graham Addis wrote:
> Hi Wolf,
>
> Not a particularly successful weekend...
>
> As --entry-point was used by other pack methods I thought the best
> option would be to add a --docker-entry-point just for the docker
> format and pass it into the build as an extra-opti
Hi Wolf,
Not a particularly successful weekend...
As --entry-point was used by other pack methods I thought the best
option would be to add a --docker-entry-point just for the docker
format and pass it into the build as an extra-option like for deb and
rpm formats.
However I couldn't work out ho
Hi Wolf,
On Thu, 1 Jun 2023 at 22:55, wolf wrote:
>
> On 2023-05-31 18:47:03 +0100, Graham Addis wrote:
> > I could use the equivalent format for --entry-point
> >
> > --entry-point executable --entry-point param1 --entry-point param2
> >
> I think that is a reasonable idea. Only downside is tha
On Thu, 1 Jun 2023 at 23:04, wolf wrote:
> I did not know Guix does not currently support the shell form. In that light
> I
> think it should not be implemented, since once your idea (arguments for entry
> point) is implemented, it will be trivial for end-user to emulate it if so
> desired.
Tha
On 2023-05-30 07:52:57 +0100, Graham Addis wrote:
> Hi Worf,
>
> Thanks for the response, see below.
>
> On Mon, 29 May 2023 at 20:41, wolf wrote:
> >
> > On 2023-05-24 18:04:47 +0100, Graham Addis wrote:
> > > Dear people,
> > >
> > > I tried to create a docker image to use in a gitlab-ci insta
On 2023-05-31 18:47:03 +0100, Graham Addis wrote:
> Hi Wolf,
>
> On Tue, 30 May 2023 at 07:52, Graham Addis wrote:
> >
> > ENTRYPOINT ["executable", "param1", "param2"] # The exec form, which
> > is the preferred form:
>
> I realised that pack takes multiple symlink(s) using
>
> --symlink /bin=
Hi Wolf,
On Tue, 30 May 2023 at 07:52, Graham Addis wrote:
>
> ENTRYPOINT ["executable", "param1", "param2"] # The exec form, which
> is the preferred form:
I realised that pack takes multiple symlink(s) using
--symlink /bin=bin --symlink /opt=opt
I could use the equivalent format for --entry-
Hi Worf,
Thanks for the response, see below.
On Mon, 29 May 2023 at 20:41, wolf wrote:
>
> On 2023-05-24 18:04:47 +0100, Graham Addis wrote:
> > Dear people,
> >
> > I tried to create a docker image to use in a gitlab-ci instance but it
> > failed because I couldn't use --entry-point="bin/sh -l
On 2023-05-24 18:04:47 +0100, Graham Addis wrote:
> Dear people,
>
> I tried to create a docker image to use in a gitlab-ci instance but it
> failed because I couldn't use --entry-point="bin/sh -l -c" or
> equivalent, basically the gitlab-runner complains that it can't run
> binaries.
Would this
Dear people,
I tried to create a docker image to use in a gitlab-ci instance but it
failed because I couldn't use --entry-point="bin/sh -l -c" or
equivalent, basically the gitlab-runner complains that it can't run
binaries.
I've managed to get it working by making some changes to guix/scripts/pac
13 matches
Mail list logo
