ok, I will take this back.
I just logged into cockpit with Administrative access and it is not
complaining at all about things not being mounted.
Weird.
On Sun, Jun 9, 2024 at 3:10 AM Javier Perez wrote:
> Hi.
>
> I just finished a new build to replace my current build. After i
Hi.
I just finished a new build to replace my current build. After installing
cockpit, and checking Storage, i noticed some warnings about the disks. It
claims that /root, /home and /var are not mounted. I think they are. I just
wonder if I am doing something wrong or weird here and I&#
If it is still relevant - There is a file /etc/cockpit/disallowed-users which
in my case has one entry: root.
Try to comment it out if you need root access. Not discussing here security
implications of this change.
Leon
___
users mailing list
On Wed, 15 Mar 2023 10:36:31 -0400
Tom Rivers wrote:
> Good morning,
>
> There are two things that I have noticed lately when performing
> upgrades using cockpit:
>
> 1) When viewing the update log in real time, the display no longer
> automatically scrolls to show new
Good morning,
There are two things that I have noticed lately when performing upgrades
using cockpit:
1) When viewing the update log in real time, the display no longer
automatically scrolls to show new entries.
2) The "Verifying" line of text above the progress indicator s
> On Fri, Mar 10, 2023, at 1:57 PM, old sixpack13 wrote:
>
> This is expected behavior right now (certainly not expected by a reasonable
> user) from a
...
Thanks
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to
opment perspective. There's a similar effect with multiple
device Btrfs in KDE and GNOME, so it's not a Cockpit issue.
https://github.com/storaged-project/udisks/issues/802
--
Chris Murphy
___
users mailing list -- users@lists.fedoraproject.or
On Sun, Mar 12, 2023 at 8:38 PM Sergio Belkin wrote:
> Thanks Richard,
>
> I have a "Red Hat Developer Subscription for Individuals" I winder if I
> can manage my subscription from Cockpit the only I find is for
> registering the system, but I get:
>
> T
Thanks Richard,
I have a "Red Hat Developer Subscription for Individuals" I winder if I can
manage my subscription from Cockpit the only I find is for registering
the system, but I get:
Traceback (most recent call last): File
"/usr/lib64/python3.11/site-packages/dbus/servic
On Sat, Mar 11, 2023 at 4:51 PM Sergio Belkin wrote:
> Hi,
> I'm wondering if Cockpit can handle Docker containers in Fedora 37. Can
> anyone confirm if this is possible or not, and if so, give me some tips on
> how to do it? I see a section for podman containers but no
Hi,
I'm wondering if Cockpit can handle Docker containers in Fedora 37. Can
anyone confirm if this is possible or not, and if so, give me some tips on
how to do it? I see a section for podman containers but not for docker ones.
Thanks in advance!
--
--
Sergio Belkin
LPIC-2 Certified -
more to read:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/thread/MNAGV2XFQOLXQAXGP2CBHOQRGVYDXD2O/
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Arggghhh
...
> UUID= /home/DATA btrfs compress=zstd:1 0 0
...
sed 's/my-uuid-here/MyMirror's-uuid/g'
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
I playing around with F37 Server, Cockpit, btrfs mirror under vbox:
created a mirror with:
mkfs.btrfs -L MyMirror -m raid1 -d raid1 /dev/sdb /dev/sdc
fetched the UUID with:
btrfs fi show
setup the /etc/fstab:
UUID= /home/DATA btrfs device=/dev/sdb,
device=/dev/sdc,compress=zstd:1 0 0
or
or in this case set) the root password. Once that's
done you, and anybody else who knows it can become root.
I log in to that workstation many times each day as root. I always create a
root password when I create a new machine.
I am asking how do I enable root login for cockpit. I do not w
run this:
>> sudo passwd
>> which will you to change (or in this case set) the root password. Once
>> that's done you, and anybody else who knows it can become root.
>
> I log in to that workstation many times each day as root. I always create a
> root password w
can become root.
I log in to that workstation many times each day as root. I always create a
root password when I create a new machine.
I am asking how do I enable root login for cockpit. I do not want to use sudo. I suppose
it may be a KDE plasma issue as I see "Fedora Linux KDE Plasma&qu
On 12/09/2022 10:50 AM, Emmett Culley via users wrote:
Yes, I can see root log in disabled by default. How to I enable root
login?
Root login is disabled because the account doesn't have a password. You
can give it one during install, but it isn't required, so most people
never realize th
On 12/9/22 9:19 AM, Peter Boy wrote:
Am 09.12.2022 um 17:47 schrieb Emmett Culley via users
:
I am not able to login to cockpit, localhost:9090, as root. I can login as a
normal user, but that isn't acceptable. Why would I even need cockpit as a
normal user?
By default, the root
> Am 09.12.2022 um 17:47 schrieb Emmett Culley via users
> :
>
> I am not able to login to cockpit, localhost:9090, as root. I can login as a
> normal user, but that isn't acceptable. Why would I even need cockpit as a
> normal user?
By default, the root login is
I am not able to login to cockpit, localhost:9090, as root. I can login as a
normal user, but that isn't acceptable. Why would I even need cockpit as a
normal user?
I have a fully updated Fedora instance. It may be related somehow to plasma as at the
top of the login dialog I see &q
On 30/09/2021 18:27, Bjoern Franke via users wrote:
Hi,
I tried to use the cockpit on fc34, but the login fails:
Sep 30 12:25:11 bfr.foo.bar.tld cockpit-session[170263]:
pam_unix(cockpit:session): session opened for user bfr(uid=1000) by (uid=0)
Sep 30 12:25:11 bfr.foo.bar.tld audit[170263
Hi,
I tried to use the cockpit on fc34, but the login fails:
Sep 30 12:25:11 bfr.foo.bar.tld cockpit-session[170263]:
pam_unix(cockpit:session): session opened for user bfr(uid=1000) by (uid=0)
Sep 30 12:25:11 bfr.foo.bar.tld audit[170263]: USER_START pid=170263
uid=0 auid=1000 ses=88 subj
> Am 17.01.2021 um 01:02 schrieb Samuel Sieb :
>
> On 1/16/21 5:31 AM, Richard Shaw wrote:
>> So as far as I can remember I haven't done anything custom here but...
>> Problem 1: package cockpit-bridge-235-1.fc33.x86_64 conflicts with
>> cockpit-dashboard <
On 1/16/21 5:31 AM, Richard Shaw wrote:
So as far as I can remember I haven't done anything custom here but...
Problem 1: package cockpit-bridge-235-1.fc33.x86_64 conflicts with
cockpit-dashboard < 233 provided by cockpit-dashboard-229-1.fc33.noarch
- cannot install the bes
On 1/16/21 3:12 PM, Peter Boy wrote:
Am 16.01.2021 um 23:07 schrieb Samuel Sieb :
That is strange. This is what I get:
# dnf install cockpit
According your list you don’t have cockpit-dashboard installed, which is the
culprit
Oops, you're right! I missed that. However:
# dnf in
> Am 16.01.2021 um 23:07 schrieb Samuel Sieb :
>
> That is strange. This is what I get:
>
> # dnf install cockpit
> Last metadata expiration check: 3:19:39 ago on Sat 16 Jan 2021 07:45:05 AM
> PST.
&g
a few days, thinking the mirrors were out of
sync, I
did the same thing to get around the problem :-(
That is strange. This is what I get:
# dnf install cockpit
Last metadata expiration check: 3:19:39 ago on Sat 16 Jan 2021 07:45:05
AM PST.
Dependencies resolved
On Sat, Jan 16, 2021 at 03:49:41PM +0100, Peter Boy wrote:
> >
> > Is it me or a packaging problem?
>
>
> I had the same problem on several servers. I just removed dashboard - not the
> best solution but the quickest.
After hitting the problem for a few days, thinking the mirrors were out of
On 1/16/21 5:31 AM, Richard Shaw wrote:
So as far as I can remember I haven't done anything custom here but...
Problem 1: package cockpit-bridge-235-1.fc33.x86_64 conflicts with
cockpit-dashboard < 233 provided by cockpit-dashboard-229-1.fc33.noarch
Looks like this is the missi
> Am 16.01.2021 um 14:31 schrieb Richard Shaw :
>
> So as far as I can remember I haven't done anything custom here but...
>
> Problem 1: package cockpit-bridge-235-1.fc33.x86_64 conflicts with
> cockpit-dashboard < 233 provided by cockpit-dashboard-229-1.fc33.noarc
So as far as I can remember I haven't done anything custom here but...
Problem 1: package cockpit-bridge-235-1.fc33.x86_64 conflicts with
cockpit-dashboard < 233 provided by cockpit-dashboard-229-1.fc33.noarch
- cannot install the best update candidate for package
cockpit-dashboard-22
Hi! Did anyone succeeded making an apache proxy to a localhost listening
cockpit service?
Thank you!!
Adrian
smime.p7s
Description: S/MIME Cryptographic Signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email
This has been going on for a while but to took several times before I
narrowed down which package was the cause.
Basically, whenever the cockpit-ws package is updated, I loose all
networking. No amount of turning ethernet off and on or restarting
NetworkManager brings it back. My only choice thus
On Tue, Jul 25, 2017 at 4:38 PM, Patrick Dupre wrote:
> Probably need to open up the port using firewall-config... I think it
> might have a cockpit checkbox but I'm still at work so I can't easily check.
>
>
> Yes, there is one, and I checked it.
> But trying to
Sent: Tuesday, July 25, 2017 at 11:21 PM
From: "Richard Shaw"
To: "Community support for Fedora users"
Subject: Re: cockpit
On Tue, Jul 25, 2017 at 4:18 PM, Patrick Dupre <pdu...@gmx.com> wrote:
Hello,
I followed the instructions of
https://linoxide.com/li
On Tue, Jul 25, 2017 at 4:18 PM, Patrick Dupre wrote:
> Hello,
>
> I followed the instructions of
> https://linoxide.com/linux-how-to/install-cockpit-fedora-
> centos-rhel-arch-linux/
>
> Then I can access locally to the service either by localhost:9090
> or by using
Hello,
I followed the instructions of
https://linoxide.com/linux-how-to/install-cockpit-fedora-centos-rhel-arch-linux/
Then I can access locally to the service either by localhost:9090
or by using the ip address.
But I cannot do it from outside.
Indeed, I need to go through a ssh port
How can I
Can cockpit manage firewalld rules?
I did not see anyway to do it on a recent server setup.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Wow, we removed this command a while ago and I guess forgot to remove
the man page.
atomic info
Will show you the labels.
Latest atomic has added --display command
atomic install imagename --display
Will show the command that will be executed without executing it.
On 08/10/2015 02:53 PM, Ro
On Mon, 10 Aug 2015, Daniel J Walsh wrote:
> Here are a couple of blogs on the atomic command
>
> http://developerblog.redhat.com/2015/04/21/introducing-the-atomic-command/
> http://www.projectatomic.io/blog/2015/04/using-environment-substitution-with-the-atomic-command/
>
> atomic command is avai
stuff like
>>>> that ... i'm using the sample Dockerfiles from the
>>>> "fedora-dockerfiles" package to demonstrate various Dockerfile
>>>> instructions in an upcoming course, and i ran across this:
>>>>
>>>> cockpit-ws/D
e sample Dockerfiles from the
>>> "fedora-dockerfiles" package to demonstrate various Dockerfile
>>> instructions in an upcoming course, and i ran across this:
>>>
>>> cockpit-ws/Dockerfile:LABEL INSTALL /usr/bin/docker run -ti --rm
>>> --privileg
package to demonstrate various Dockerfile
> > instructions in an upcoming course, and i ran across this:
> >
> > cockpit-ws/Dockerfile:LABEL INSTALL /usr/bin/docker run -ti --rm
> > --privileged -v /:/host IMAGE /container/atomic-install
> > cockpit-ws/Dockerfile:LABEL U
ng course, and i ran across this:
>
> cockpit-ws/Dockerfile:LABEL INSTALL /usr/bin/docker run -ti --rm --privileged
> -v /:/host IMAGE /container/atomic-install
> cockpit-ws/Dockerfile:LABEL UNINSTALL /usr/bin/docker run -ti --rm
> --privileged -v /:/host IMAGE /cockpit/atomic-uninst
brief digression from my discussion of docker roadmap and stuff like
that ... i'm using the sample Dockerfiles from the
"fedora-dockerfiles" package to demonstrate various Dockerfile
instructions in an upcoming course, and i ran across this:
cockpit-ws/Dockerfile:LABEL INSTALL
On Tue, 19 May 2015 12:58:40 +0200
arnaud gaboury wrote:
> When connecting to cockpit, from Firefox or chromium, I get this error
> when looking at the JS console:
>
> TypeError: l.GetUnitFileState is not a function1 shell.js:38:3271
> TypeError: c.Subscribe is not a function1 b
When connecting to cockpit, from Firefox or chromium, I get this error
when looking at the JS console:
TypeError: l.GetUnitFileState is not a function1 shell.js:38:3271
TypeError: c.Subscribe is not a function1 bundle.js:2:8289
I can still browse and see pages.
Any idea why and how to fix it
48 matches
Mail list logo
