"Select Working Directory" ends with "ERROR: Is a directory" #302

New Issue

GiteaMirror · 2025-10-31T15:08:02-05:00

GiteaMirror commented

2025-10-31 15:08:02 -05:00

Originally created by @F1zzyD on GitHub (Apr 21, 2025).

I am trying to import my existing docker compose files into Komodo. According to the docs HERE, I should just need to create a stack, ensure it has access to the compose files using the "Store the files anywhere on host" option, and make sure I define the project name. Here's what happened:

Selecting the "Run Directory" to the absolute path where my compose.yaml file is located causes Komodo go give me an error "Failed" followed by "Is a directory (os error 21). If I'm reading this right, Komodo wants me to give me a directory for the docker-compose file, but gets made because it is a directory... this doesn't make sense, especially when the grayed empty text literally says "/path/to/folder".
Per the docs, "In order for Komodo to pick up a running project, it has to know the compose "project name". You can find the project name by running docker compose ls on the host. By default, Komodo will assume the Stack name is the compose project name.". I put in the project name when creating the stack which is the exact name of the project when running docker ps. Komodo does nothing to pick up the running project.
When running with just the project name and no "Run Directory" in hopes for Komodo to pick up the project, it gives me an error "A compose file doesn't exist after writing stack. Ensure the run_directory and file_paths are correct.". Again, no import takes place.

Is there actually a way to import compose.yaml files in Komodo currently, or is this just one of those features that is coming and not yet implemented?

Originally created by @F1zzyD on GitHub (Apr 21, 2025). I am trying to import my existing docker compose files into Komodo. According to the docs [HERE](https://komo.do/docs/docker-compose), I should just need to create a stack, ensure it has access to the compose files using the "Store the files anywhere on host" option, and make sure I define the project name. Here's what happened: - Selecting the "Run Directory" to the absolute path where my compose.yaml file is located causes Komodo go give me an error "Failed" followed by "Is a directory (os error 21). If I'm reading this right, Komodo wants me to give me a directory for the docker-compose file, but gets made because it is a directory... this doesn't make sense, especially when the grayed empty text literally says "/path/to/folder". - Per the docs, _"In order for Komodo to pick up a running project, it has to know the compose "project name". You can find the project name by running docker compose ls on the host. By default, Komodo will assume the Stack name is the compose project name."_. I put in the project name when creating the stack which is the exact name of the project when running `docker ps`. Komodo does nothing to pick up the running project. - When running with just the project name and no "Run Directory" in hopes for Komodo to pick up the project, it gives me an error "A compose file doesn't exist after writing stack. Ensure the run_directory and file_paths are correct.". Again, no import takes place. Is there actually a way to import compose.yaml files in Komodo currently, or is this just one of those features that is coming and not yet implemented?

GiteaMirror closed this issue

2025-10-31 15:08:02 -05:00

GiteaMirror commented

2025-10-31 15:08:03 -05:00

@Owen000 commented on GitHub (Apr 27, 2025):

Same issue

@Owen000 commented on GitHub (Apr 27, 2025): Same issue

GiteaMirror commented

2025-10-31 15:08:03 -05:00

@mbecker20 commented on GitHub (Apr 28, 2025):

Periphery running in container will have separate file system. You can mount the directories you need in, making sure the path is same both inside and outside container, or use systemd periphery to avoid the file system separation

@mbecker20 commented on GitHub (Apr 28, 2025): Periphery running in container will have separate file system. You can mount the directories you need in, making sure the path is same both inside and outside container, or use systemd periphery to avoid the file system separation

GiteaMirror commented

2025-10-31 15:08:04 -05:00

@F1zzyD commented on GitHub (Apr 28, 2025):

Got it figured out. Yes, periphery needs access to the filesystem but it wasn't clear that both sides needed to be the exact same AND you must remove the periphery tag at the very front, otherwise it will go to a different directory. Working with other docker containers, Komodo does not allow you to make shortcuts to make entering things in easy. For example, you must ALWAYS use the absolute directory; you cannot do something like /home/user/docker:/docker

@F1zzyD commented on GitHub (Apr 28, 2025): Got it figured out. Yes, periphery needs access to the filesystem but it wasn't clear that both sides needed to be the exact same AND you must remove the periphery tag at the very front, otherwise it will go to a different directory. Working with other docker containers, Komodo does not allow you to make shortcuts to make entering things in easy. For example, you must ALWAYS use the absolute directory; you cannot do something like /home/user/docker:/docker

GiteaMirror commented

2025-10-31 15:08:04 -05:00

@mbecker20 commented on GitHub (Apr 29, 2025):

You set PERIPHERY_ROOT_DIRECTORY, if you don't enter any run directory it will assume $PERIPHERY_ROOT_DIRECTORY/stacks/$stack_name as the run directory and you can give paths relative to that.

@mbecker20 commented on GitHub (Apr 29, 2025): You set PERIPHERY_ROOT_DIRECTORY, if you don't enter any run directory it will assume $PERIPHERY_ROOT_DIRECTORY/stacks/$stack_name as the run directory and you can give paths relative to that.

GiteaMirror referenced this issue

2025-10-31 15:19:27 -05:00

[PR #248] [MERGED] 1.17.0 #713

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/komodo#302