Azure Container Registry and ACI not working

[BlackHornet]

I created an image based on jenkins/ssh-slave and pushed it to my private Container Registry in Azure.

When I now configure the ACI container template it isn't working correctly, the container is always restarted.
Running the image locally on my machine is working.

Or is there an issue with the definition of the private docker registry?

[gavinfish]

@yuwzho Could you please take a look when you are free, thanks.

[BlackHornet]

What is the actual docker run command used to launch the container on the Linux machine?

Maybe there is also an issue with the Dockerfile itself in that case?

[yuwzho]

Would you like to share your Dockerfile? Or simplify it before sharing?

And what's the command and launch method in your configuration?

[BlackHornet]

Hi,

As a side note:
My intention was to create a container based on jenkins/ssh-slave that also has the functionality of thyrlian/android-sdk being able to build Android applications.

I guess it is an issue with my Dockerfile.

Dockerfile.txt

With RUN chmod -R 777 /opt/android-sdk the container won't start and keeps restarting.

Without RUN chmod -R 777 /opt/android-sdk the container is starting, but my build fails due to noted comment in Dockerfile

* What went wrong:
A problem occurred configuring project ':app'.
> Failed to install the following SDK components:
      platforms;android-28 Android SDK Platform 28
      build-tools;27.0.3 Android SDK Build-Tools 27.0.3
  The SDK directory is not writable (/opt/android-sdk)

I hope you can help me out solving this issue, as I really would like to have my Android builds running in an ACI.

Thank you in advance.

[yuwzho]

Seems this is a permission issue. 777 seems too crazy for a /opt/XXX folder. How about 666 or 664? Check the current priviledge may help to get the right access number. Or just chmod -R +w /opt/android-sdk.