You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2024. It is now read-only.
I couldn't see any documentation about how containers are named, and it's not easy to find in the code either. I did eventually find it - it seems the suffix is project_id and comes from the inode number of the containing folder.
Worth adding a note to the documentation?
The text was updated successfully, but these errors were encountered:
Maybe worth adding something short about this. As far as I know the reason for this is that some people may want to clone the same project in two locations, do a lxdock up, and end up with two differently named containers.
This issue should be about being able to customize this. I don't like having this. In my scripting I have to parse lxd outputs to do anything with the container.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using the sample lxdock.yml, I get containers whose names are
<project name>-<container name>-<some digits>
.I couldn't see any documentation about how containers are named, and it's not easy to find in the code either. I did eventually find it - it seems the suffix is
project_id
and comes from the inode number of the containing folder.Worth adding a note to the documentation?
The text was updated successfully, but these errors were encountered: