Skip to content
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

Make k8s.io a default nerdctl namespace and/or user-configurable #1266

Open
1 task done
dee-kryvenko opened this issue Jan 18, 2022 · 2 comments
Open
1 task done

Make k8s.io a default nerdctl namespace and/or user-configurable #1266

dee-kryvenko opened this issue Jan 18, 2022 · 2 comments
Labels
area/config kind/enhancement New feature or request

Comments

@dee-kryvenko
Copy link

Preflight Checklist

  • I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Problem Description

nerdctl -n k8s.io build is long to type.

Proposed Solution

Make k8s.io a default namespace or make it configurable by the user, so in result -n k8s.io don't have to be typed in.

Additional Information

No response

@dee-kryvenko dee-kryvenko added the kind/enhancement New feature or request label Jan 18, 2022
@mook-as
Copy link
Contributor

mook-as commented Feb 28, 2022

See relevant minikube PR — we can set worker.containerd.namespace in buildkitd.toml for that.

@jandubois
Copy link
Member

See relevant minikube PR — we can set worker.containerd.namespace in buildkitd.toml for that.

That doesn't sounds right. The default namespace should be the same for all nerdctl commands, not just build. The obvious mechanism is to set CONTAINERD_NAMESPACE=k8s.io.

IF #1279 is implemented (and it is currently being considered for the release after 1.1.0), then this would already work (when set on the host).

We could still add a configuration option in the GUI to set this inside the VM, the way we already provide a default for CONTAINERD_ADDRESS.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/config kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants