/cake/Cake: Permission denied

[cake-build]

/cake/Cake: Permission denied

[devlead]

Interesting, cake --info and Cake --info works though. x would indicate execute bit is there.

What does your your docker file look like? Or how are you launching the container?

[gitfool]

From WSL, via docker run --rm -it cakebuild/cake:v0.32.1-2.1-sdk.

From Azure Pipelines, via Cake.Dungeon/azure-pipelines.yml#L10, in which I may be missing something as that build is my very first attempt to build with a Docker container on Azure Pipelines.

cake --info and Cake --info do work when I run them inside the container.

Note however that the executable bit is missing (for group and others) from /cake/Cake, as I showed above:

root@aab27beb84ed:/src# ls -al /cake/Cake
-rwxrw-rw- 1 root root 97416 Jan  4 20:42 /cake/Cake

[devlead]

Bit is there for the executing user though

Container only has root user.

Other wise neither cake --info nor Cake -info should work.

With the yaml you link to I would assume the bash build step runs on the VM and not the container.

In general without a Docker file you can only run one command with docker run, a workaround would be something like docker run --rm -it cakebuild/cake:v0.32.1-2.1-sdk /bin/bash -c "cake --botstrap && cake"

A yaml step in Azure Pipelines could look something like

- task: Docker@1
  displayName: 'Run an image'
  inputs:
    containerregistrytype: 'Container Registry'

    command: 'Run an image'

    imageName: 'cakebuild/cake:v0.32.1-2.1-sdk'

    volumes: '$(Build.Repository.LocalPath):/repository'

    workingDirectory: /repository

    containerCommand: '/bin/bash -c "cake --botstrap && cake"'

    runInBackground: false

you could also have a Dockerfile in repo

Then step would look something like

- task: Docker@1
  displayName: 'Build image'

And a Dockerfile could look something like

FROM cakebuild/cake:v0.32.1-2.1-sdk AS builder

ADD .  /src

WORKDIR src

RUN  Cake --bootstrap && Cake

[gitfool]

I suspect it's to do with how Azure Pipelines runs the build steps. They add a user to the container, and according to Container jobs requirements, they "will docker exec a series of commands which expect to be run by a shell"; so you can have many build steps and each is run separately via docker exec.

[devlead]

Ok I see, I've merged your PR, if I compiles CI should have a new container out in a couple minutes.

[devlead]

A new v0.32.1-2.1-sdk is now on docker hub.

[gitfool]

Success! 😃

[devlead]

Excellent 👍