no command to rename an instance?

Bug #1531357 reported by James Troup
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxd (Ubuntu)
Fix Released
Low
Stéphane Graber

Bug Description

Perhaps I'm just being dense (and if so, I apologize) but I can't seem to find any way to rename an instance once its launched. That seems unfortunate?

Revision history for this message
Tycho Andersen (tycho-s) wrote : Re: [Bug 1531357] [NEW] no command to rename an instance?

Hi James,

On Wed, Jan 06, 2016 at 01:54:14AM -0000, James Troup wrote:
> Public bug reported:
>
> Perhaps I'm just being dense (and if so, I apologize) but I can't seem
> to find any way to rename an instance once its launched. That seems
> unfortunate?

I think "lxc move" should be what you want, whether or not it behaves
correctly locally right now (there are a few bugs filed about this).
"lxc move foo bar" should change the name on the local host.

Revision history for this message
Stéphane Graber (stgraber) wrote :

We should probably reword the lxc move help a bit to help clarify.

Changed in lxd (Ubuntu):
status: New → Triaged
importance: Undecided → Low
assignee: nobody → Stéphane Graber (stgraber)
Revision history for this message
Stéphane Graber (stgraber) wrote :

I reworked the help quite a bit to help with this, patch is pending upstream review.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lxd - 0.27-0ubuntu1

---------------
lxd (0.27-0ubuntu1) xenial; urgency=medium

  * New upstream release (0.27)
    - Support for container disk quota (zfs and btrfs only)
    - Download progress during image copy and container launch (LP: #1530414)
    - Initial work on a LXC to LXD script (supports almost every
      configuration except for unprivileged containers)
    - New linux.kernel_modules container property (list of modules to
      load before starting the container)
    - New core.https_allowed_origin server property (controls the
      Access-Control-Allow-Origin header)
    - Profile changes are now live-applied to all affected containers
    - "lxc config edit" now works against servers too
    - Changes to security.nesting are now live-applied
    - Support for xfs with the lvm backend
    - "lxc image list" now supports filtering (by name, hash and properties)
    - Improved bash completion profile
    - The default remote is now visible in "lxc remote list"
    - "lxc info" now indicates whether a container is ephemeral or persistent
    - Various improvement to help messages
      (LP: #1531643, LP: #1530413, LP: #1531357)
    - A lot of bugfixes and other performance improvement, see:
      https://linuxcontainers.org/lxd/news/

 -- Stéphane Graber <email address hidden> Wed, 20 Jan 2016 09:53:05 -0500

Changed in lxd (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.