Sharing tmp directory across multiple commands in a snap app

Bug #1552458 reported by Rajendra Dendukuri
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Triaged
Wishlist
Unassigned

Bug Description

Here is an application which has a central daemon app and multiple commands. These commands are exposed as commands to user and connect to the central daemon app.

Assume that central daemon creates unix domain sockets in /tmp folder and expects the commands to read and write to them. When we start porting this application to Snappy it is observed that /tmp seen by commands is not same as that seen by central daemon app. Please note that all the commands and central daemon is being packaged into a single SNAP.

Given that we do not want to change the /tmp handling of application, does Snappy provide an automatic way to handle it.

I also observed that for each invocation of a command a throw away tmp directory is created. There is no cleanup of them and it tends to grow overtime.

http://pastebin.com/vPryWH9V

I am using xenial ubuntu-core daily image dated 3/1/2016

Revision history for this message
Loïc Minier (lool) wrote :

Hi Jamie,
would you think this is fixable for 16.04?
Thanks,
- Loïc

Michael Vogt (mvo)
Changed in snappy:
status: New → Triaged
importance: Undecided → Wishlist
Michael Vogt (mvo)
affects: snappy → snapd
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.