--tmp / -t option isn't available in python-vm-builder 0.12.2-0ubuntu3

Bug #539231 reported by Randy Barlow
36
This bug affects 6 people
Affects Status Importance Assigned to Milestone
VMBuilder
New
Undecided
Unassigned
vm-builder (Ubuntu)
Fix Released
Medium
Serge Hallyn
Lucid
Won't Fix
Undecided
Unassigned
Maverick
Won't Fix
Undecided
Unassigned

Bug Description

The version of python-vm-builder that came with Karmic had a -t flag that you could use to specify where the VM should be built. This was handy, as it allowed me to build the VM on a tmpfs that I mounted manually (since the --tmpfs flag didn't work). This flag isn't accepted by the new version that comes with Lucid, and there doesn't seem to be any replacement for its functionality.

Mathias Gug (mathiaz)
Changed in vm-builder (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Randy Barlow (rbarlow) wrote :

If I may, I'd like to contend that this is not a duplicate of bug #536940. That ticket is about having a --tmpfs flag that will allow us to indicate that we wish the VM to be built in a tmpfs. That ticket is also marked as a wishlist item. This ticket is about having a flag that allows us to specify a path at which we would like the VM to be built. The -t flag can be used to build in tmpfs, but it can also be used to build in /home or wherever else I would like. What if my system had a small /tmp partition, but I had space somewhere else? Also, this flag should be a good bit simpler to implement that --tmpfs. Can we please have both flags? If not, I'd prefer this one over --tmpfs, personally. Thank you for your consideration!

Revision history for this message
Soren Hansen (soren) wrote :

You're absolutely right. Sorry. I thought -t was short for --tmpfs.

Revision history for this message
Randy Barlow (rbarlow) wrote :

Hey Soren, thanks for your consideration!

Revision history for this message
Randy Barlow (rbarlow) wrote :

Also, I just spoke with the powers that pay my salary, and I have received a green light to write a patch for this ticket. I'm gonna get started on that now. I've never contributed to Ubuntu before, but I assume that the standard procedure it to attach a patch to this ticket?

Revision history for this message
Randy Barlow (rbarlow) wrote :

I made a commit to the branch for this ticket. I've definitely gotten it to use the -t flag in some places, but there are still files being created in /tmp. I haven't yet identified the code that is placing files in there, but for now I can't spend any more time on this. Hopefully my work is a good start for someone to finish this!

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Yes, please don't break backwards compatbility anymore. I'm a big fan of partitioning, and my / partition is small. ubuntu-vm-builder is now barfing in lucid that -t is not available, and it runs out of disk space when using /tmp. It also doesn't seem to honor TMPDIR.

Revision history for this message
Rafal-maj-it (rafal-maj-it) wrote :

So.. any fix? workaround?

summary: - -t option isn't available in python-vm-builder 0.12.2-0ubuntu3
+ --tmp / -t option isn't available in python-vm-builder 0.12.2-0ubuntu3
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Hi Randy,

did you ever write a patch for this?

Revision history for this message
Rafal-maj-it (rafal-maj-it) wrote :

workaround:
TMPDIR=./foo
export TMPDIR
vmbuilder ....

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

I just did

mount -t tmpfs tmpfs tmp
vmbuilder kvm ubuntu --suite=lucid --mirror=http://localhost:3142/us.archive.ubuntu.com/ubuntu -t /srv/serge/vmbuilder/tmp

and it is currently building in /srv/serge/vmbuilder/tmp:

root@sergelap:/srv/serge/vmbuilder# ls tmp
tmpFuRGkB tmpjYJS25

This is in natty, though. Which release are you on? I'll request an SRU of the fix.

Changed in vm-builder (Ubuntu):
assignee: nobody → Serge Hallyn (serge-hallyn)
status: Triaged → In Progress
Changed in vm-builder (Ubuntu):
status: In Progress → Fix Released
Changed in vm-builder (Ubuntu Lucid):
status: New → Confirmed
Changed in vm-builder (Ubuntu Maverick):
status: New → Confirmed
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

The fix came in as part of bzr commit #37. Neither lucid nor maverick have that yet.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Please let me know if the proposed packages (in comment #12 and #12) work for you. If they do, I'll request an SRU.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

maverick has seen the end of its life and is no longer receiving any updates. Marking the maverick task for this ticket as "Won't Fix".

Changed in vm-builder (Ubuntu Maverick):
status: Confirmed → Won't Fix
Revision history for this message
Rolf Leggewie (r0lf) wrote :

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

Changed in vm-builder (Ubuntu Lucid):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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