Hook into container build process

[mu88]

Hi 👋🏻

First, I want to highlight how great your project is working 💪🏻 I migrated several of my apps from building the Docker image via Dockerfile to using the SDK Container Building Tools and it works super smooth.

When doing so, an idea/question came to my mind. With the current solution, I see no way to migrate this Dockerfile. While I might somehow could move the custom PowerShell/Playwright installation logic into a dedicated image and use that as base image, this line will make me fall over the favor SDK Container Building Tools over Dockerfile cliff 😉

To support such use cases, it would be cool to somehow hook into the container building process, allowing to add calls like RUN ....

[baronfel]

Thanks for the kind words - it's always great to hear that folks are having success with the tooling :)

You've hit the kind of situation of think about a lot - this idea of the "Dockerfile complexity cliff" is something we've really tried to address. For RUN commands we can't really address those for the fundamental reason that there is no Linux VM that we could run the commands in - though we do have an issue for using a local Dockerfile as the base image for the running application.

I'm very curious about the chmod line you highlighted though - why did you need to add that to the container?

[mu88]

That gives the following:

$ ls -la /home/app/data
total 8
drwxr-xr-x 2 1001 1001 4096 Nov 28 16:02 .
drwxr-xr-x 1 app  app  4096 Nov 29 06:54 ..

[baronfel]

Ok, that's a clue! It looks like the ownership of the data directory is 1001:1001 instead of app:app.

The bad news is this - there doesn't seem to be a way to set the permissions on a volume that's mounted from the Docker CLI: https://stackoverflow.com/a/56990338

Answers suggest creating a volume inside the container during container creation, but unfortunately we don't support Volumes in the SDK tech.

So I think you may be in a bit of a wall with the rootless execution at the moment. We can look at implementing Volume support as it's clear to me that is a key part of the overall rootless end to end story.

[mu88]

Thx for your explanations - I'm learning a lot :)

I agree that volumes are an essential part, therefore having support for that in the SDK would be great. Do you have an issue for me that I can subscribe to? With that, I think we could close this discussion.

[baronfel]

We added one just over a week ago here: #526

I'm going to add a comment to this issue based on our discussion here right now!