-
|
Has anyone else seen this, is there a way to see what jib created for a dockerfile to try to debug? |
Beta Was this translation helpful? Give feedback.
Replies: 10 comments 14 replies
-
Beta Was this translation helpful? Give feedback.
-
|
Are you use you have enough disk space? I've never seen |
Beta Was this translation helpful? Give feedback.
-
|
Perhaps Kind does not, I had just upgraded my Kind cluster version so
perhaps something went wrong with the StorageSystem, I'll check it.
Brett Tofel
he/him/his
Sr. Software Engineer
Red Hat (OpenShift Operator Portfolio Enablement / OLM)
…On Fri, Apr 8, 2022 at 1:42 AM Georgios Andrianakis < ***@***.***> wrote:
Are you use you have enough disk space?
I've never seen java.nio.file.FileSystemException: /tmp/vertx-cache: No
space left on device before
—
Reply to this email directly, view it on GitHub
<#24827 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABB6HL6JRRRXWTR6B663DTTVD7BKFANCNFSM5S2P6NWA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hmm, nope, I reverted Kind as the easiest way to check if that upgrade was the culprit and it's still the same error... And it's not a general problem with the Kind cluster: I made a busybox based pod that had shell script on entry to mkdir a dir in /tmp and write to it. Runs without error or special config. Something broke in the past few weeks and I'm unable to determine what, but my code didn't change. It's a little bit of a pain, but I'm going to verify same thing works on CRC or a clusterbot cluster now. This will at least say if it's something just with Kind. |
Beta Was this translation helpful? Give feedback.
-
|
Works on CRC. This is Kind specific but not something that broke going from 0.11.1 to 0.12.0, something that stopped working with Kind in Quarkus or perhaps even the OpenJDK base since I don't have that pinned. |
Beta Was this translation helpful? Give feedback.
-
|
I'd really like to be able to do my debug/test cycle with Kind, any hints for debugging this problem? |
Beta Was this translation helpful? Give feedback.
-
|
What exactly are you looking to do? |
Beta Was this translation helpful? Give feedback.
-
|
Start a Quarkus-based Operato on a Kind cluster. It did work and now is failing with this vertx error... |
Beta Was this translation helpful? Give feedback.
-
|
And it only happens on a Kind cluster? I've personally never used Kind, so can't help much. |
Beta Was this translation helpful? Give feedback.
-
|
There is some mismatch between the Quarkus generated container image and Kind. I added a command to a manual deployment of the operator image to drop into a shell, then I compared operations from the shell on my operator image to a busybox image: my operator on Kind cluster: versus Is there any way to get a sense of like the Dockerfile that backs the Quarkus operator image? |
Beta Was this translation helpful? Give feedback.
-
|
I made the change by adding: but that landed me at: |
Beta Was this translation helpful? Give feedback.
-
|
Please try specifying a concrete directory |
Beta Was this translation helpful? Give feedback.
-
|
So I searched for what seemed like an okay place by poking around on the image running successfully on CRC. I have this info from that poking around: So I chose to set |
Beta Was this translation helpful? Give feedback.
-
|
I am completely out of ideas |
Beta Was this translation helpful? Give feedback.
-
|
I going to try swapping back to the older bases you suggested and see if I can identify a diff point |
Beta Was this translation helpful? Give feedback.
-
|
But something changed. This was working fine with Kind. Maybe I can set like the Quarkus base image back to try to get a diff of working vs. non-working... How would I do that? Currently looks like the image is based on: |
Beta Was this translation helpful? Give feedback.
-
|
Here are the various changes that were made to the base image: You can set the base image manually using https://quarkus.io/guides/all-config#quarkus-container-image-jib_quarkus.jib.base-jvm-image |
Beta Was this translation helpful? Give feedback.
-
|
Actually I'm a little confused how I would specify an older base image? |
Beta Was this translation helpful? Give feedback.
-
|
Don't know about the SHA, but you can use the names you can find in the PRs |
Beta Was this translation helpful? Give feedback.
-
|
Ah, I figured it out, like this: But the bad news is: I went back to 1.11-2 and 1.10 (3 and 4 months back) and same error. Is there anything else, that I can mess with, that might have changed without me making an explicit change in the POM? |
Beta Was this translation helpful? Give feedback.
-
|
Not that I can think of |
Beta Was this translation helpful? Give feedback.
-
|
Figured it out. Docker was out of space. |
Beta Was this translation helpful? Give feedback.
Figured it out. Docker was out of space.
docker prunefixed it. FWIW, this is a Kind shortcoming, because when I went to install minikube, on cluster start it pointed out that Docker was out of space and suggested fixes.