Skip to content

Fix: Make the config field optional #1309

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.

Sign up for GitHub

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

Merged
sudo-bmitch merged 1 commit into from
Feb 26, 2026
+2 −2
Merged

Fix: Make the config field optional #1309

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion config.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,7 +131,7 @@ Note: Any OPTIONAL field MAY also be set to null, which is equivalent to being a
- **config** _object_, OPTIONAL

The execution parameters which SHOULD be used as a base when running a container using the image.
This field can be `null`, in which case any execution parameters should be specified at creation of the container.
If the `config` object is omitted, any execution parameters should be specified at creation of the container.

- **User** _string_, OPTIONAL

Expand Down
2 changes: 1 addition & 1 deletion specs-go/v1/config.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,7 @@ type Image struct {
Platform

// Config defines the execution parameters which should be used as a base when running a container using the image.
Config ImageConfig `json:"config,omitempty"`
Config ImageConfig `json:"config,omitzero"`
Comment thread
sudo-bmitch marked this conversation as resolved.

// RootFS references the layer content addresses used by the image.
RootFS RootFS `json:"rootfs"`
Expand Down