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
The Base class can accept an optional compatibility_tag. If a compatibility_tag is not provided and craft-providers launches LXD instances for 2 different projects, LXD will fail because the two base instances have identical names.
* Command standard error output: b'Error: Failed start validation for device "eth0": Instance DNS name "base-instance-buildd-base-v3-craft-comub-523148486bd0c6cc722c" already used on network\nTry `lxc info --show-log local:base-instance-buildd-base-v3-craft-comub-523148486bd0c6cc722c` for more info\n'
The text was updated successfully, but these errors were encountered:
Bug Description
The
Base
class can accept an optionalcompatibility_tag
. If acompatibility_tag
is not provided and craft-providers launches LXD instances for 2 different projects, LXD will fail because the two base instances have identical names.Source: canonical/craft-application#139
Quick fix
craft-providers should log a warning if a compatibility tag is not provided:
Long term fix
As part of a major release, the
compatibility_tag
should be easier to use. It should be required and prepended to the base's compatibility tag.This simply the usage from:
to:
To Reproduce
part yaml
No response
Relevant log output
The text was updated successfully, but these errors were encountered: