Sample Header Ad - 728x90

Unix & Linux Stack Exchange

Q&A for users of Linux, FreeBSD and other Unix-like operating systems

Latest Questions

0 votes
1 answers
64 views
Problems updating /etc/hosts file via command bash -c
Trying to update host configuration file via command : $ sudo bash -c 'echo $(minikube ip) blue.io green.io >> /etc/hosts' Command was passed, but host configuration file /etc/hosts was not updated. If after command above, I pass the following command: $ sudo bash -c 'echo $(minikube ip) blue.io gre...
Trying to update host configuration file via command : $ sudo bash -c 'echo $(minikube ip) blue.io green.io >> /etc/hosts' Command was passed, but host configuration file /etc/hosts was not updated. If after command above, I pass the following command: $ sudo bash -c 'echo $(minikube ip) blue.io green.io | cat' The following message is returned: "Profile "minikube" not found. Run "minikube profile list" to view all profiles. 👉 To start a cluster, run: "minikube start" blue.io green.io. If I run command below: $ sudo nano /etc/hots I can see two times the following message at the bottom of the script: "Profile "minikube" not found. Run "minikube profile list" to view all profiles. 👉 To start a cluster, run: "minikube start" blue.io green.io. I resorted to updating file manually using nano command, by deleting message from above, and entering a line manually: xxx.xxx.99.100 blue.io green.io $ nano /etc/hosts I wonder why code sudo bash -c.... did not update configuration file as expected. Further information: - code is run on a ubuntu Linux VM with enabled nested virtualisation, - running a minikube cluster(kubernetes) - 2 configuration maps are setup to customise each of the webservers from a yaml file I read posts like [Webserver /etc/hosts file questions](https://unix.stackexchange.com/questions/710857/webserver-etc-hosts-file-questions) but I could not find the answer to my question.
josepmaria (103 rep)
Oct 30, 2024, 05:38 PM • Last activity: Oct 30, 2024, 09:49 PM
1 votes
0 answers
365 views
How do I install specific old versions of snaps, and is there a way I can find their dependency versions ahead of time?
I'm trying to install snapcraft on a Beaglebone Blue, which is running: ``` debian@beaglebone:~$ uname -a Linux beaglebone 4.19.94-ti-r42 #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC 2020 armv7l GNU/Linux ``` But when I do, I get this error: ``` debian@beaglebone:~$ sudo snap install snapcraft --cla...
I'm trying to install snapcraft on a Beaglebone Blue, which is running:
debian@beaglebone:~$ uname -a
Linux beaglebone 4.19.94-ti-r42 #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC 2020 armv7l GNU/Linux
But when I do, I get this error:
debian@beaglebone:~$ sudo snap install snapcraft --classic
error: cannot perform the following tasks:
- Mount snap "core22" (1034) (snap "core22" assumes unsupported features: snapd2.55.5 (try to update snapd and refresh the core snap))
When I try to upgrade snapd I get this:
debian@beaglebone:~$ sudo apt-get upgrade snapd
Reading package lists... Done
Building dependency tree       
Reading state information... Done
snapd is already the newest version (2.37.4-1+deb10u3).
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
My plan is to find the oldest version of core22 that works on snapd version 2.37.4, and then find the version of snapcraft that uses that version of core22. I've visited the core22 github repo, and couldn't find past versions. It doesn't look like they have a release structure. If this is feasible, how could I do that? If it isn't feasible, is there any other way to get microk8s on this machine?
KerPop47 (11 rep)
Jan 6, 2024, 07:49 PM
1 votes
0 answers
108 views
minikube and ingress-dns issues with fedora and virtualbox?
I followed that setup instructions (I'm new to K8s) https://minikube.sigs.k8s.io/docs/handbook/addons/ingress-dns/ I enabled ingress-dns and that Ok. I added `dns=dnsmasq` in NetworkManager.conf I added `server=/test/$(minikube ip)` in /etc/NetworkManager/dnsmasq.d/minikube.conf ``` nslookup hello-j...
I followed that setup instructions (I'm new to K8s) https://minikube.sigs.k8s.io/docs/handbook/addons/ingress-dns/ I enabled ingress-dns and that Ok. I added dns=dnsmasq in NetworkManager.conf I added server=/test/$(minikube ip) in /etc/NetworkManager/dnsmasq.d/minikube.conf
nslookup  hello-john.test $(minikube ip)                                                                                                                                                                                                                                                            
Server:		192.168.59.100
Address:	192.168.59.100#53

Non-authoritative answer:
Name:	hello-john.test
Address: 192.168.59.100
that works. But if i try without specifying the minikube IP it does not anymore.
nslookup  hello-john.test                                                                                                                                                                                                                                                                    
Server:		127.0.0.53
Address:	127.0.0.53#53

** server can't find hello-john.test: NXDOMAIN
so I edited the systemd/resolved.conf and added the minikube IP. Then here it works fine, ... except for the extrnal domains, which are failing then using a fallback. What Am I missing here?
thiebaut fischer (11 rep)
Dec 20, 2023, 03:05 PM
3 votes
1 answers
3752 views
How can I make the minikube dashboard answer on all ips 0.0.0.0?
`minikube` has a dashboard that I can view easily with minikube dashboard However, that only works if I run it on my own machine because it only answers on localhost, * Verifying dashboard health ... * Launching proxy ... * Verifying proxy health ... * Opening http://127.0.0.1:35781/api/v1/namespace...
minikube has a dashboard that I can view easily with minikube dashboard However, that only works if I run it on my own machine because it only answers on localhost, * Verifying dashboard health ... * Launching proxy ... * Verifying proxy health ... * Opening http://127.0.0.1:35781/api/v1/namespaces/kubernetes-dashboard/services/http:kubernetes-dashboard:/proxy/ in your default browser... - http://127.0.0.1:35781/api/v1/namespaces/kubernetes-dashboard/services/http:kubernetes-dashboard:/proxy/ I'm running minikube though on a remote machine on openstack, so I need to address it by it's lan address, and not 127.0.0.1.
Evan Carroll (34663 rep)
Nov 24, 2020, 07:50 PM • Last activity: Nov 24, 2020, 07:51 PM
0 votes
2 answers
282 views
Can docker pull an image visable in podman and buildah?
If I run `buildah images`, I see an image that is fully visable and functional with `podman` and `buildah` toolchain, $ buildah images REPOSITORY TAG IMAGE ID CREATED SIZE localhost/foobar-centos-7 92 688ca4049c1e 24 hours ago 4.13 GB localhost/centos-base 7 fec48054ea4d 24 hours ago 325 MB However,...
If I run buildah images, I see an image that is fully visable and functional with podman and buildah toolchain, $ buildah images REPOSITORY TAG IMAGE ID CREATED SIZE localhost/foobar-centos-7 92 688ca4049c1e 24 hours ago 4.13 GB localhost/centos-base 7 fec48054ea4d 24 hours ago 325 MB However, minikube doesn't yet work with Podman v2, and the driver is experimental with v1. I need these images to available to docker, which underscores minikube and is the only supported driver. Note, I don't want to have to push to an external registry or set up quay.
Evan Carroll (34663 rep)
Nov 23, 2020, 03:30 AM • Last activity: Nov 24, 2020, 04:27 PM
0 votes
1 answers
1572 views
Why does minikube require passwordless sudo for podman?
[Minikube specifies](https://minikube.sigs.k8s.io/docs/drivers/podman/#known-issues), > Podman requirements passwordless running of sudo. If you run into an error about sudo, do the following: They suggest adding username ALL=(ALL) NOPASSWD: /usr/bin/podman However, this must be very insecure as now...
[Minikube specifies](https://minikube.sigs.k8s.io/docs/drivers/podman/#known-issues) , > Podman requirements passwordless running of sudo. If you run into an error about sudo, do the following: They suggest adding username ALL=(ALL) NOPASSWD: /usr/bin/podman However, this must be very insecure as now you could do, sudo podman run -ti -v /etc/shadow:/etc/shadow:rw alpine:3 /bin/sh And not have to authenticate. Why is this requirement in place? Is there an alternative?
Evan Carroll (34663 rep)
Nov 20, 2020, 04:51 PM • Last activity: Nov 20, 2020, 06:12 PM
Showing page 1 of 6 total questions