hi, I have the following structure: • train/ ◦ semantic_segmentation/ ▪︎ BUILD ▪︎ config/ • docker/ ◦ semantic_segmentation/ ▪︎ BUILD The folder config/ has config files distributed among subfolders. I need to have this folder in the working dir of my docker file: I saw in the docks that the .PEX file cannot included files (that we can use

open

), so inside the build file, I defined the docker file:

docker_image(
    name="gpu",
    dependencies = ["docker:base_docker_gpu", "train/semantic_segmentation"],
    instructions = [
        "FROM base_docker_gpu",
        "COPY train.semantic_segmentation/train.pex /bin",
        "COPY train/semantic_segmentation/config /root/",
    ]
)

But the copy instruction fails (

./pants package docker/semantic_segmentation:gpu

):

COPY failed: file not found in build context or excluded by .dockerignore: stat train/semantic_segmentation/config: file does not exist

I tired to add the config folder as a target with the files target:

files(
    name="semantic_segmentation_config",
    sources=["config/*/*", "config/*.yaml", "config/*/*.yaml"],
)

So, what would be the right way to add the config/ folder to my docker image using?

Add the "semantic_segmentation_config" target to the dependencies field of the docker_image target. That should ensure that the files are included in the build context.

In some cases, such as when copying a single file, pants can infer the dependency on that file. But here you're copying the entire dir, so pants can't infer the dependency, and you have to add it manually

I have tried:

docker_image(
    name="gpu",
    dependencies = ["//:clearml", "docker:base_docker_gpu", "train/semantic_segmentation:semantic_segmentation_config"],
    instructions = [
        "FROM base_docker_gpu",
        "COPY train.semantic_segmentation/train.pex /bin",
        "COPY train/semantic_segmentation/config /root/",
    ]
)

The image builds ok, but the /root folder is empty.

OK, so the fact that the image builds tells me that

train/semantic_segmentation/config

exists in the context, but apparently it's empty

```files(

name="semantic_segmentation_config",

sources=["config/*/*", "config/*.yaml", "config/*/*.yaml"],

)```

It seems like you may want

config/**/*.yaml

maybe it should just be be

sources=["config/**/*.yaml"],

Thanks, it worked with

config/**/*.yaml

You can bundle it as a

resource

into the pex itself

Thanks, I read in the docs that, as a resource, they cannot be normally accessed, .e.g by

open

, that holds? Or they will get unpacked with the rest of the .pex?

It depends on how the pex is built and run. If it's a venv-mode pex then it creates a regular venv, so you should be able to do whatever you could do in a venv

Thanks, it worked by adding the files as

resources

and setting the

.pex

execution mode to

venv

.