exo

exo copied to clipboard

see title - it's b/c compose namespaces by type, and we namespace within a workspace

What would we consider a good solution to this? Should we just adopt any volume that happens to have the appropriate name?

This bug is unrelated to component adoption. It's more similar to having invalid characters in the name. We should detect conflicts on import and add a suffix or something to the component name (but not the container/volume/network name in docker) to disambiguate them.

And if we do this, we should emit a warning :)

Oh sorry, I understand. This is about volumes and networks with the same name as each other. I thought it was about conflicting with docker compose.

Added "good first issue" because this should be entirely contained within compose/convert.go and similar to res.AddRenameWarning(originalName, name)