Different problems, mainly related to the amount of user namespaces.
Trying to run a pre-built image yields:
podman run --rm -it -p8080:8080 --env LOGSTASH_CONF_STRING=$LOGSTASH_CONF_STRING --name logstash bitnami/logstash:latest
Completed short name "bitnami/logstash" with unqualified-search registries (origin: /etc/containers/registries.conf)
Trying to pull docker.io/bitnami/logstash:latest...
Getting image source signatures
# layers
Writing manifest to image destination
Storing signatures
Error processing tar file(exit status 1): potentially insufficient UIDs or GIDs available in user namespace (requested 0:4 for /var/log/apt/term.log): Check /etc/subuid and /etc/subgid: lchown /var/log/apt/term.log: invalid argument
Trying to pull quay.io/bitnami/logstash:latest...
Getting image source signatures
# layers...
Storing signatures
Error processing tar file(exit status 1): potentially insufficient UIDs or GIDs available in user namespace (requested 0:4 for /var/log/apt/term.log): Check /etc/subuid and /etc/subgid: lchown /var/log/apt/term.log: invalid argument
Error: 2 errors occurred while pulling:
* Error committing the finished image: error adding layer with blob "sha256:8a5e287f7d41a454c717077151d24db164054831d7cd1399ee81ab2dfba4bcb2": Error processing tar file(exit status 1): potentially insufficient UIDs or GIDs available in user namespace (requested 0:4 for /var/log/apt/term.log): Check /etc/subuid and /etc/subgid: lchown /var/log/apt/term.log: invalid argument
* Error committing the finished image: error adding layer with blob "sha256:8a5e287f7d41a454c717077151d24db164054831d7cd1399ee81ab2dfba4bcb2": Error processing tar file(exit status 1): potentially insufficient UIDs or GIDs available in user namespace (requested 0:4 for /var/log/apt/term.log): Check /etc/subuid and /etc/subgid: lchown /var/log/apt/term.log: invalid argument
So I can't really run this thing. Then trying to run a locally built container which creates a user I get:
Error: OCI runtime error: container_linux.go:370: starting container process caused: setup user: invalid argument
Configuration has been set up with subuid
jmerelo:100000:65536
Although
podman unshare cat /proc/self/uid_map
0 1000 1
So there must be something that I'm missing or that I should restart here. Even if I log in again, it's still the same result. So there must be something that I'm doing wrong here.
Same problem solved by following this:
rm -rf ~/.config/containers ~/.local/share/containers
podman system migrate
Related
Jenkins pipeline is building Docker images. OpenShift plugin(s) are used for the same.
An example command:
openshift.selector(BUILD_CONFIG_NAME, "${appBcName}").startBuild("--from-dir=${artifactPath}", '--wait','--follow')
While this works smoothly most of the time, whenever this command fails due to some underlying platform issues, almost no information is seen in the Jenkins build job console:
[Pipeline] }
[start-build:buildconfig/amld5-car-reporting-spacetime-ubi-openshift-java-runtimejd] ............................................................
[start-build:buildconfig/amld5-car-reporting-spacetime-ubi-openshift-java-runtimejd] Uploading finished
[start-build:buildconfig/amld5-car-reporting-spacetime-ubi-openshift-java-runtimejd] Error from server (BadRequest): unable to wait for build amld5-car-reporting-spacetime-ubi-openshift-java-runtimejd-857 to run: timed out waiting for the condition
[Pipeline] }
ERROR: Error running start-build on at least one item: [buildconfig/amld5-car-reporting-spacetime-ubi-openshift-java-runtimejd];
{err=, verb=start-build, cmd=oc --server=https://api.scp-west-zone02-z01.net:6443 --certificate-authority=/var/run/secrets/kubernetes.io/serviceaccount/ca.crt --namespace=sb-1166-amld5-car-service-se --token=XXXXX start-build buildconfig/amld5-car-reporting-spacetime-ubi-openshift-java-runtimejd --from-dir=./build/libs --wait --follow -o=name , out=Uploading directory "build/libs" as binary input for the build ...
............................................................
Uploading finished
Error from server (BadRequest): unable to wait for build amld5-car-reporting-spacetime-ubi-openshift-java-runtimejd-857 to run: timed out waiting for the condition
, status=1}
[Pipeline] // catchError
I need more verbosity, detailed error information. I checked the start-build command reference, and I thought --build-loglevel [0-5] might help here. When I used it, I got a warning that since I am using source type as 'Binary' in the BuildConfig, logging isn't supported(seriously???)
NOTE: the selector returned when -F/--follow is supplied to startBuild() will be inoperative for the various selector operations.
Consider removing those options from startBuild and using the logs() command to follow the build output.
[start-build:buildconfig/casc-docs-spacetime-ubi-openshift-java-runtimeadoptopenjdk] WARNING: Specifying --build-loglevel with binary builds is not supported.
[start-build:buildconfig/casc-docs-spacetime-ubi-openshift-java-runtimeadoptopenjdk] WARNING: Specifying environment variables with binary builds is not supported.
[start-build:buildconfig/casc-docs-spacetime-ubi-openshift-java-runtimeadoptopenjdk] Uploading directory "build/libs" as binary input for the build ...
[start-build:buildconfig/casc-docs-spacetime-ubi-openshift-java-runtimeadoptopenjdk] ..
How do I get more logs, info. while executing the start-build command?
I was facing the same problem, I just used something like:
def build = openshift.selector(BUILD_CONFIG_NAME, "${appBcName}").startBuild("--from-dir=${artifactPath}", '--wait','--follow')
build.logs('-f')
And so far it seems to work, I got the logs from my openshift build in my Jenkins pipeline. Now I'll try to get the logs only if build does not Complete, to reduce the overall logs.
(for future searchers like me ^^)
I attempt to load gnome-boxes from the terminal (I'm running Fedora 33) and get the following error
$ gnome-boxes
(gnome-boxes:3194): Gtk-WARNING **: 12:34:57.343: GtkFlowBox with a model will ignore sort and filter functions
(gnome-boxes:3194): Gtk-WARNING **: 12:34:57.344: GtkListBox with a model will ignore sort and filter functions
(gnome-boxes:3194): Boxes-WARNING **: 12:34:57.904: libvirt-machine.vala:83: Failed to disable 3D Acceleration
(gnome-boxes:3194): Boxes-WARNING **: 12:34:57.913: libvirt-broker.vala:70: Failed to update domain 'fedora33-wor-2': Failed to set domain configuration: XML error: Invalid PCI address 0000:04:00.0. slot must be >= 1
(gnome-boxes:3194): Boxes-CRITICAL **: 12:34:57.916: boxes_vm_importer_get_source_media: assertion 'self != NULL' failed
Segmentation fault (core dumped)
My system:
$uname -a
Linux localhost.localdomain 5.9.16-200.fc33.x86_64 #1 SMP Mon Dec 21 14:08:22 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
I don't whether it's related but I recently updated from kernel 5.9.11 directly to 5.9.16 (haven't used the PC in question for some weeks) and before gnome-boxes was working as normal.
Please advise how I can restore gnome-boxes - I have some virtual machines that I need to access...
I faced this issue when I force stopped Gnome-Boxes while cloning a VM.
Deleting the conflicting VM will resolve your issue(in your case 'fedora33-wor-2').
To delete the VM in fedora, install "libvirt-client" which provides "virsh" using the command
dnf install libvirt-client
then double check the available VM's using
virsh list --all
Delete the VM using command,
virsh undefine VM_Name
#channel-fun solved the problem of staring up gnome-boxes.
But the real problem is in cloning procedure. The XML describing the new machine is malformed.
virt-clone --original fedora33-ser --auto-clone
works properly.
I know this is an old thread, but I had the same problem recently.
I shut down gnome boxes whilst it was cloning a vm, and shutdown the machine.
I then couldn't open boxes, as it would just crash.
I was able to delete the VM itself, and then deleted the XML file associated with it.
To delete the VM itself, go to :
$HOME/.var/app/org.gnome.Boxes/data/gnome-boxes/images (which in my case is a symbolic link to a data drive)
and delete the VM with the name that you were cloning to (or safer, just move it somewhere).
To delete the XML file associated with it:
$HOME/.var/app/org.gnome.Boxes/config/libvirt/qemu/
and delete (or safer move) the file that is named VM_NAME.xml.
Then boxes should open ok, at least it worked for me.
Extending on Channel Fun's answer for Ubuntu repos the package is libvirt-clients (note the plural s):
sudo apt install libvirt-clients
Check the available VM's using:
virsh list --all
Delete the VM using:
virsh undefine VM_Name
If you receive the error:
error: Refusing to undefine while domain managed save image exists
Then you can explicitly remove that also using the --managed-save flag:
virsh undefine VM_Name --managed-save
I am trying to run uefi code in qemu for beagle board using the following command
qemu-system-arm -M beagle -sd beagle_sd.img -serial stdio -clock unix
The sdcard holds uefi, which starts the shell, when this runs I am getting sd card error saying CMD17 is a wrong state. My log
SD: CMD17 in a wrong state
sd_read_data: not in Sending-Data state (state=0)
----above line prints multiple times
sd_read_data: not in Sending-Data state (state=0)MmcIoBlocks(MMC_CMD65553): Error Device Error
EhcCreateUsb2Hc: capability length 0
EhcDriverBindingStart: failed to create USB2_HC
Due to this my uefi shell only maps blk0 and blk1.
Any ideas on how to ahead?
I am trying to run the MIT project CryptoDB. I have downloaded it and I have followed the instructions to compile as it is explained in the included instructions, for mysql-proxy and mysql version 5.5.14. I am using a RedHat Enterprise 6 server.
When I get to the point of running the make command i get this error:
Building CXX object sql/CMakeFiles/sql.dir/sql_lex.cc.o
In file included from /soft/mysql-5.5.14/build/sql/lex_hash.h:25,
from /soft/mysql-5.5.14/sql/sql_lex.cc:113:
/soft/mysql-5.5.14/sql/lex.h:193: error: ‘ENC_SYM’ was not declared in this scope
/soft/mysql-5.5.14/sql/lex.h:623: error: too many initializers for ‘SYMBOL’
make[2]: *** [sql/CMakeFiles/sql.dir/sql_lex.cc.o] Error 1
make[1]: *** [sql/CMakeFiles/sql.dir/all] Error 2
make: *** [all] Error 2
I am quite lost as I cannot find if there is a missing library or any kind of incompatbility on what I am using. Any ideas?
Even i have not finished installation now I now that the problem comes from not having the last version of the code. By getting it with the following command:
git clone -b public git://g.csail.mit.edu/cryptdb
I get to execute an instalation script in ruby that performs the work.
The script is not writen especifically for Redhat, so I am having some work adapting some commands (apt-get => yum).
I am trying to produce a memory (simple dual port ram) using core generator in xilinx 14.2. The problem is that during synthesis says :
ERROR:sim - Failed to run command ' -p xc3s100e-5cp132 -sd
"C:/Users/ORiON/register_file/ipcore_dir/tmp/_cg/_dbg/" -sd
"C:/Users/ORiON/register_file/ipcore_dir/tmp/_cg/" -dd
"C:/Users/ORiON/register_file/ipcore_dir/tmp/_cg/_dbg/" "MEM_aRd_sWr_16x32"
"C:/Users/ORiON/register_file/ipcore_dir/tmp/_cg/MEM_aRd_sWr_16x32.ngc"
-intstyle xflow'. Executable file not found.
ERROR:sim - Failed executing Tcl generator.
Wrote CGP file for project 'MEM_aRd_sWr_16x32'.
Core Generator create command failed.
ERROR:sim - Failed to generate 'MEM_aRd_sWr_16x32'. Failed executing Tcl
generator.
The command itself is missing.
Failed to run command 'A_COMMAND_SHOULD_BE_HERE -p xc3s100e-5cp132 -sd
I assume it's a kind of script or makefile who is calling this command and the command is defined as a variable. And the variable is not assigned. Something like that?