Skip to content

Conversation

jeromegn
Copy link
Contributor

Description of changes:

The way InitrdPath was implemented is buggy:

  • When you set a initrd_path with firecracker, you do not want a root drive.
  • There was a type (I believe that's what it was) which prevented initrdFilename to ever be set to anything other than "". This would make the config for InitrdPath useless.

With both these changes, I was able to use initrd_path successfully.

@jeromegn
Copy link
Contributor Author

jeromegn commented Dec 1, 2020

Actually, I wonder if having a root drive is at odds with an initrd. As in: you can't have a root drive if you have an initrd.

@jeromegn
Copy link
Contributor Author

Anyone want to look into this?

@kzys
Copy link
Contributor

kzys commented Dec 14, 2020

Hey. Sorry for the late reply. We've fixed the Go 1.11 issue on master. Could you rebase this branch?

initrdFilename was always blank because it wasn't assigned w the right scope.

don't need to validate that a root drive is present when an InitrdPath is present

Signed-off-by: Jerome Gravel-Niquet <[email protected]>
@kzys
Copy link
Contributor

kzys commented Dec 14, 2020

Looks good to me. Can you remove go mod tidy from this PR? Your PR doesn't bring any new dependencies and go.mod changes would cause conflict with others such as #290.

@jeromegn
Copy link
Contributor Author

My bad, I wanted to make all the tests pass. Looks like another one is failing in the firecracker suite.

@kzys
Copy link
Contributor

kzys commented Dec 14, 2020

Yes. There were a few root-owned files which BuildKite Agent couldn't remove.

@kzys kzys merged commit fc167ff into firecracker-microvm:master Dec 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants