Skip to content

Conversation

@solventak
Copy link

@solventak solventak commented Nov 12, 2025

Closes #791 , #665

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update

Motivation and Context

Add createdAt metadata (generic metadata struct) for each Container, Volume, and Network as well as output in ls commands to display it.

Also fixes a bug when spawning networkvmnet.service where instead of initializing the network configuration from the stored information of NetworkConfiguration entity it would create a new configuration based on key metadata that was passed in through args.

Testing

  • Tested locally
  • Added/updated tests
  • Added/updated docs

Signed-off-by: alex-trm <alex.kennedy@trmlabs.com>
Signed-off-by: alex-trm <alex.kennedy@trmlabs.com>
createdAt getter

Signed-off-by: alex-trm <alex.kennedy@trmlabs.com>
@solventak
Copy link
Author

@jglogan for your consideration :)

@solventak solventak changed the title Feature/resource createdat container startedat Add createdAt and metadata to container, network, and volume resources Nov 12, 2025
@jglogan
Copy link
Contributor

jglogan commented Jan 5, 2026

@solventak Sorry, this one fell through the cracks an I didn't get around to reviewing it.

If you're still interested in moving this one forward, please take a look at #1020 as it gives us a more sustainable base for your work.

I'm thinking that our resource types (container, image, volume, network, and possibly others later; for example kernels) in ContainerResource could conform to an Identifiable-conforming ContainerResource protocol along the lines of what you have here. That protocol could have a metadata property that has createdAt and labels.

Let us know here if you're interested in tackling this.

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.

3 participants