https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# rancher-desktop
a
This message was deleted.
q
This message contains interactive elements.
(This is what I get when I launch RD)
k
My first guess is that it's complaining about the high-bit character (unless that's a slack artefact). Let me get a second opinion...
From the look of that error message, it looks like all the text after 
9p:\n
got dropped.
q
the high-bit char is not a slack artifact, but I also didn't invent that content, I'm 99% confident I copy+pasted it
f
I don't know if the warning is what is breaking the logic here, but you could try removing the unsupported fields and see if that fixes it.
q
I did, I got another error instead 🙂
f
Ok, please show that one. The warning should be just a warning...
q
This message contains interactive elements.
btw, I have questions about 
limactl.ventura copy
answer: 
copy
is not part of the file name
(it's impossible for me to naively parse that string correctly between the various unquoted spaces)
f
It is the subcommand; essentially a wrapper around 
scp
q
Copy code
lima-rancher-desktop:/Users/jsoref$ df -h /tmp/
Filesystem                Size      Used Available Use% Mounted on
/dev/disk/by-label/data-volume
                         97.9G     97.0G         0 100% /mnt/data
f
Is the VM running? Can you create a shell? Is there space in the VM?
q
yes. yes. no.
f
Well, there you go then 😞
q
...
everyone else gets garbage-collected, why not me? 🙂
f
Because you are not running k8s?
q
also, wtf is eating my space?
oh, well, there is that 🙂
i mean, i'm not really running much of anything atm 😉
f
It is either dangling images, or build caches
q
what was the stupid command to ask?
Copy code
lima-rancher-desktop:/Users/jsoref$ docker system

Usage:  docker system COMMAND

Manage Docker

Commands:
  df          Show docker disk usage
  events      Get real time events from the server
  info        Display system-wide information
  prune       Remove unused data

Run 'docker system COMMAND --help' for more information on a command.
lima-rancher-desktop:/Users/jsoref$ docker system info
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.10.4
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx

Server:
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
errors pretty printing info
i don't think i can talk to docker 😉
f
I know. If there is nothing else for you to delete, then the only other option is to increase the size of the volume a bit
q
please say this mess is fixed in 1.9.1 .... the only reason i'm here is i naively quit 1.9.0 so i could restart it to see if it'd offer me an upgrade to 1.9.1.
f
This may require you to have more than 100GB of free space on your machine though
q
+1k / +1m / +1g?
Copy code
lima-rancher-desktop:/Users/jsoref$ df -h .
Filesystem                Size      Used Available Use% Mounted on
mount0                  926.4G    792.9G    133.4G  86% /Users/jsoref
i think it'd be better for me to ask RD to shoot everything. I don't need anything I have. Will that work?
Anyway, I'm voting for "this is a serious/major regression since 1.8.x"
f
Yes, factory-reset should work
q
Did someone file a ticket for this mess, or do I get to? 🙂
f
It is not a regression. Using 100% of available space in the volume always prevented you from starting again
q
But I've been using RD since 1.0 or before and this is the first time I've run into problems and my usage habits haven't changed significantly
f
If you have the time/patience, maybe increase the size of the VM to be able to start, and then look where the memory went?
q
how much time? I can certainly run the command and do other things
I presume i'm running that command from outside 
rdctl shell
(quitting RD now)
f
Yes, shut down Rancher Desktop, make sure the VM is stopped, and then run the command on the host
q
Copy code
jsoref@jsoref-mbp ~ % ps aux|grep Rancher
jsoref           39485   0.0  0.0 408495824   1072 s326  R+   12:42PM   0:00.00 grep Rancher
jsoref@jsoref-mbp ~ %
f
It should be quick. Then restart RD; it will grow the partition to use the additional space
q
Copy code
jsoref@jsoref-mbp ~ % /Applications/Rancher\ <http://Desktop.app/Contents/Resources/resources/darwin/lima/bin/qemu-img|Desktop.app/Contents/Resources/resources/darwin/lima/bin/qemu-img> resize "$HOME/Library/Application Support/rancher-desktop/lima/0/diffdisk" +10G
WARNING: Image format was not specified for '/Users/jsoref/Library/Application Support/rancher-desktop/lima/0/diffdisk' and probing guessed raw.
         Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
         Specify the 'raw' format explicitly to remove the restrictions.
Image resized.
jsoref@jsoref-mbp ~ %
f
Then you can install the "Disk Usage" extension and take a look
q
do i have to wait for the vm to start?
f
Yes, you need the container engine because extensions need to be pulled from Docker Hub
q
Do I want to know how I can have 64 dangling things that have a size of 0B?
f
You can also run it from the CLI:
Copy code
$ docker system df
TYPE            TOTAL     ACTIVE    SIZE      RECLAIMABLE
Images          11        6         515.8MB   264.4MB (51%)
Containers      13        11        0B        0B
Local Volumes   0         0         0B        0B
Build Cache     0         0         0B        0B
q
Copy code
jsoref@jsoref-mbp ~ % docker system df

TYPE            TOTAL     ACTIVE    SIZE      RECLAIMABLE
Images          133       41        44.11GB   32.51GB (73%)
Containers      83        0         4.795GB   4.795GB (100%)
Local Volumes   42        16        9.339GB   124.1MB (1%)
Build Cache     402       0         28.01GB   28.01GB
the numbers seem to agree, so that's good, i guess
f
You can run 
docker system prune
to reclaim space...
If you add 
--all
it will remove all images not currently in use by containers, so much more aggressive
q
This message contains interactive elements.
Untitled
f
I wonder if some recent changes made the build cache grow much faster than before
q
maybe?
i think i'd like to prune the images that have no tags
i.e. most of the cat-the-hacker
but, even so, that shouldn't justify this
Copy code
% docker system prune
WARNING! This will remove:
  - all stopped containers
  - all networks not used by at least one container
  - all dangling images
  - all dangling build cache

Are you sure you want to continue? [y/N]
Is the plural of 
cache
also 
cache
??
f
I think it should be 
caches
, but I'm not a native speaker
q
as a native speaker, I agree.
and as someone who will not touch the docker project w/ a 10' pole, that's as far as I'm going.
f
I think here they mean "all dangling build cache items"
q
also fine
what's here is not fine 🙂
or even 
all dangling build cache entries
cute, while 
docker system prune
is running, 
docker system df
and friends hang
really friendly ux there.
f
q
Nope. I will not touch their org w/ a 10' pole. I'm serious on that point.
f
Me, I have a meeting now; the officially sanctioned alternative to working 😛
😆 1
q
They threatened to ban me and I'm not interested dealing w/ them.
the 
docker system prune
never finished
f
q
Hours?
I killed it just now and started it when you suggested it?
This message contains interactive elements.
f
Try 
rdctl shutdown
q
Copy code
jsoref@jsoref-mbp ~ % rdctl shutdown
Rancher Desktop is currently not running (or can't be shutdown via this command).
hmm, RD is gone
ok, starting again, what should I do? I want to trigger a prune, but can i monitor it?
f
You should be able to run 
docker system df
in a second shell
I'm not sure what all these screenshots are supposed to tell me, except that you are not running 1.9.1 yet (which shouldn't make a difference for this issue)
q
Copy code
jsoref@jsoref-mbp ~ % docker system df
TYPE            TOTAL     ACTIVE    SIZE      RECLAIMABLE
Images          133       41        44.11GB   32.51GB (73%)
Containers      83        0         4.795GB   4.795GB (100%)
Local Volumes   42        16        9.339GB   124.1MB (1%)
Build Cache     402       0         28.01GB   28.01GB
jsoref@jsoref-mbp ~ %
So, the previous attempts (based on your earlier suggestion) yielded:
Copy code
jsoref@jsoref-mbp ~ % docker system prune
WARNING! This will remove:
  - all stopped containers
  - all networks not used by at least one container
  - all dangling images
  - all dangling build cache

Are you sure you want to continue? [y/N] y
^C
jsoref@jsoref-mbp ~ % docker system prune
WARNING! This will remove:
  - all stopped containers
  - all networks not used by at least one container
  - all dangling images
  - all dangling build cache

Are you sure you want to continue? [y/N] y
^C
jsoref@jsoref-mbp ~ % rdctl shell
^C
This message contains interactive elements.
Untitled
Copy code
Total reclaimed space: 53.71GB
f
Sounds good
q
Copy code
lima-rancher-desktop:/Users/jsoref$ df -h /tmp/
Filesystem                Size      Used Available Use% Mounted on
/dev/disk/by-label/data-volume
                        107.7G     36.7G     65.5G  36% /mnt/data
so basically the previous attempts got wedged before they did anything
f
Looks like it. We have no control over what happens there; it is all docker software...
46 Views
Open in Slack
PreviousNext
Powered by