-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add machine table to containers.conf #782
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -54,6 +54,8 @@ type Config struct { | |
Containers ContainersConfig `toml:"containers"` | ||
// Engine specifies how the container engine based on Engine will run | ||
Engine EngineConfig `toml:"engine"` | ||
// Machine specifies configurations of podman machine VMs | ||
Machine MachineConfig `toml:"machine"` | ||
// Network section defines the configuration of CNI Plugins | ||
Network NetworkConfig `toml:"network"` | ||
// Secret section defines configurations for the secret management | ||
|
@@ -281,9 +283,6 @@ type EngineConfig struct { | |
// MachineEnabled indicates if Podman is running in a podman-machine VM | ||
MachineEnabled bool `toml:"machine_enabled,omitempty"` | ||
|
||
// MachineImage is the image used when creating a podman-machine VM | ||
MachineImage string `toml:"machine_image,omitempty"` | ||
Comment on lines
-284
to
-285
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This field is not in podman 3.3, right? In this case I would want this PR and the podman wiring to get into podman 3.4 so that we do not have to worry about backwards compat for this field. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes this is not in 3.3 |
||
|
||
// MultiImageArchive - if true, the container engine allows for storing | ||
// archives (e.g., of the docker-archive transport) with multiple | ||
// images. By default, Podman creates single-image archives. | ||
|
@@ -490,6 +489,18 @@ type SecretConfig struct { | |
Opts map[string]string `toml:"opts,omitempty"` | ||
} | ||
|
||
// MachineConfig represents the "machine" TOML config table | ||
type MachineConfig struct { | ||
// Number of CPU's a machine is created with. | ||
CPUs uint64 `toml:"cpus,omitempty"` | ||
// DiskSize is the size of the disk in GB created when init-ing a podman-machine VM | ||
DiskSize uint64 `toml:"disk_size,omitempty"` | ||
// MachineImage is the image used when init-ing a podman-machine VM | ||
Image string `toml:"image,omitempty"` | ||
// Memory in MB a machine is created with. | ||
Memory uint64 `toml:"memory,omitempty"` | ||
} | ||
|
||
// Destination represents destination for remote service | ||
type Destination struct { | ||
// URI, required. Example: ssh://[email protected]:22/run/podman/podman.sock | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we go ahead and add cpus?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I can wire that in now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And I guess memory as well?