Skip to content
This repository has been archived by the owner on Oct 17, 2022. It is now read-only.

Manage multiple auraed instances #16

Open
krisnova opened this issue Sep 26, 2022 · 3 comments
Open

Manage multiple auraed instances #16

krisnova opened this issue Sep 26, 2022 · 3 comments
Labels

Comments

@krisnova
Copy link
Contributor

Right now we can start 2 auraed instances... we shouldn't be able to do that

@MalteJ
Copy link
Contributor

MalteJ commented Oct 1, 2022

If we decide to integrate firecracker into auraed, we'd need to spawn a second, "jailed", auraed instance from the main (pid 1) auraed instance. This second instance would then act as the MicroVM's hypervisor.

If you simply try to start two auraed instances in parallel, there'll be an error that the socket is already in use.
I'm not sure if we really got a problem with multiple auraed instances.

@MalteJ
Copy link
Contributor

MalteJ commented Oct 1, 2022

ahh sorry, I haven't tested starting auraed twice.
The problem is this line:

let _ = fs::remove_file(&self.socket);

During initialization of auraed we remove the socket if it already exists. Probably the file descriptor stays open so the first auraed keeps running, but the file is gone and replaced by the second auraed's socket.

@MalteJ
Copy link
Contributor

MalteJ commented Oct 1, 2022

Probably the above mentioned line should be removed completely.
Instead we should delete the socket during auraed's shutdown as described in #36

@MalteJ MalteJ added the Bug label Oct 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants