Installing "en_US" in RHEL container [closed] - docker

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
I'm testing an ansible role using molecule. The role install a corporate binary over which I've no insight, I'm just mean to ./binary --silent and that's it. Over RedHat.
It work for a RedHat 6.9 VM. But it doesn't work over the docker container registry.access.redhat.com/rhel6:6.9.
The error message says:
"Operating system bad language (en_US not found)".
What could be missing from the container that would be on the VM? Some localedef ...? I wasn't able to find a doc about this, but is there some RedHat description about the delta between their "minimal install from ISO" VMs and containers?
Thanks for any help

If you run locale -a on the Docker image you're using, you'll get the following output:
C
en_US.utf8
POSIX
Run the same command in your VM and compare output. If it contains line en_US (without utf-8 suffix), try adding the following lines dicrectly below FROM directive in your Dockerfile:
RUN localedef -v -c -i en_US -f UTF-8 en_US; exit 0
RUN sed -i 's/en_US.UTF-8/en_US/g' /etc/sysconfig/i18n && source /etc/sysconfig/i18n
This will generate locale en_US with encoding UTF-8 named en_US (without any suffix).

Related

Google Coral : hide kernel boot messages [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
How to hide kernel boot message on the Google Coral ?
# cat /etc/debian_version
10.0
but i can't find the grub file (i tried, like for debian, /etc/default/grub ... nothing) to edit and add "quiet" (like for a regular Ubuntu/Debian), then regenerate grub :(
embeded linux usually uses uboot instead of grub as it is too large. Specifics on how to customizing kernel should take more researches, however, you can add loglevel=0 to the kernel command line to eliminate some kernel messages.
Download boot.txt:
$ curl https://coral.googlesource.com/uboot-imx-debian/+/refs/heads/master/debian/boot.txt\?format\=TEXT | base64 --decode | tee boot.txt > /dev/null
Install mkimage:
$ sudo apt install u-boot-tools
Make your necessary changes in the cmdline="" line, for this example, we need to add "quiet loglevel=0":
cmdline=<preexsisting> + quiet loglevel=0
compile to boot.scr:
$ mkimage -A arm -T script -O linux -d boot.txt boot.scr
replace old boot image file
$ mv boot.scr > /boot
Reboot and the new kernel params should be loaded.
share edit delete flag

I'm getting error "Public key for jenkins-2.232-1.1.noarch.rpm is not installed" while installing AWS on Jenkins [closed]

Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 2 years ago.
The community reviewed whether to reopen this question 5 months ago and left it closed:
Not suitable for this site This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I'm installing Jenkins on AWS EC2 CentOS instance. I'm following this tutorial for installation - "https://medium.com/#itsmattburgess/installing-jenkins-on-amazon-linux-16aaa02c369c". I'm getting the below error while installation.
Downloading packages:
warning: /var/cache/yum/x86_64/7/jenkins/packages/jenkins-2.232-1.1.noarch.rpm: Header V4 RSA/SHA512 Signature, key ID 45f2c3d5: NOKEY:00 ETA
Public key for jenkins-2.232-1.1.noarch.rpm is not installed
jenkins-2.232-1.1.noarch.rpm | 63 MB 00:01:49
Where am i getting wrong?
Correct public key URL can be found on Jenkins Redhat Packages page.
Just run the command below to import it:
Long Term Support release:
sudo rpm --import https://pkg.jenkins.io/redhat-stable/jenkins.io.key
Weekly release:
sudo rpm --import https://pkg.jenkins.io/redhat/jenkins.io.key
Here is an issue with details WEBSITE-741.
Updated: Jenkins installation handbook was updated with instructions on how to import proper public keys for LTS and weekly release.
More details: Jenkins 2.235.3: New Linux Repository Signing Keys.
Updated: They've updated their key URL to the following - import this key as part of the setup instead and the yum install call should function without issues and not require disabling the gpg check:
https://pkg.jenkins.io/redhat/jenkins.io.key
Original answer: I've also been hitting this. The team has apparently updated their key, but haven't updated the docs or published the new public key component and the one located at http://pkg.jenkins-ci.org/redhat/jenkins-ci.org.key isn't valid any longer. For now you can run a yum install with GPG check disabled just to get past the initial install Jenkins:
yum install jenkins --nogpgcheck
Once they've published the new public key, you'll want to import it with the rpm --import [url] call per usual so that yum update will work as expected.
Issue got resolved. Instead of the command "sudo wget -O /etc/yum.repos.d/jenkins.repo http://pkg.jenkins-ci.org/redhat/jenkins.repo" i used "sudo wget -O /etc/yum.repos.d/jenkins.repo https://pkg.jenkins.io/redhat-stable/jenkins.repo
"and it was working. Than's every for viewing my question and taking time to answer it.

Install package on Travis-ci with sudo:false [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
How can I Iinstall a package on Travis-ci with sudo:false in travis.yml ?
I have my travis.yml :
sudo: false
install:
- wget http://security.ubuntu.com/ubuntu/pool/main/i/icu/libicu52_52.1-3ubuntu0.4_amd64.deb
- sudo dpkg -i libicu52_52.1-3ubuntu0.4_amd64.deb
I have an error :
sudo: must be setuid root
The command "sudo dpkg -i libicu52_52.1-3ubuntu0.4_amd64.deb" failed and exited with 1 during .
Yes you can, at least some.
Travis has a whitelist of allowed packages you can install from using the containerised environment. Instead of using wget and dpkg, or apt, you define the packages in your yaml under the addons section. Check https://docs.travis-ci.com/user/installing-dependencies/.
In the yaml you'd have something like:
addons:
apt:
packages:
- ncftp
ncftp is whitelisted here.
If you need packages which are not whitelisted, you can set sudo: true and your build will be launched in a non-containerised environment, so you have root (sudo) access to install whatever you want. Alternatively you can raise an issue on their Github to add a whitelist for your package.

Is there a startup file (like .bashrc) for i3 where i can set environmet variables? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
It would help me to setup my system-wide proxy. I'm using latest Ubuntu and tried /etc/X11/xinit/xinitrc ~/.xinitrc and ~/.xsession,
export HTTP_PROXY=http://....
But that did not work.
Apparently i3 uses sh to launch stuff, and does not source $PATH from ~/.bashrc :
cat ~/.xsession-errors
(...)
/bin/sh: 1: mycommand: not found
So, just create a ~/.xsessionrc file and put your statements in it :
export HTTP_PROXY=http://....
Then logout and back in ; It should work now.
System-wide environment can be setup by placing a script in /etc/profile.d/
For example, you may create /etc/profile.d/proxy with your
export HTTP_PROXY=http:// # enter your proxy settings here
Then chmod +x this file, then reboot :
chmod +x /etc/profile.d/proxy
systemctl reboot
After reopening your session you could check the variables are there :
env | grep HTTP
You should see the variables set with the values you entered in the profile script.
In order to set system wide proxy settings you can add the following:
export http_proxy='http://172.27.100.5:4444/'
export https_proxy='http://172.27.100.5:4444/'
export ftp_proxy='http://172.27.100.5:4444/'
export no_proxy='localhost,127.0.0.0/8,::1
to your bash.bashrc file which is located in /etc folder. Of course, you should replace addresses with your ones. It works at least for Debian.

Elastic beanstalk and httpd.conf file? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I deployed a rails app to an elastic beanstalk application and I'm running into a Phusion Passenger timeout when I try to start my app.
The following instances have not responded in the allowed command timeout time (they might still finish eventually on their own): [i-d3fc9cf2].
I read I can make the timeout longer by modifying the httpd.conf file but I'm going crazy trying to find it. I've ssh'd into my ec2 instance and I cant find a httpd/apache folder or file anywhere.
Here's my /etc folder where I'm expecting an httpd folder:
[etc]$ ls
acpi crontab fstab issue man.config pm rpc sudoers
adjtime cron.weekly gai.conf issue.net maven popt.d rpm sudoers.d
aliases csh.cshrc gcrypt java mime.types ppp rsyslog.conf sudo-ldap.conf
aliases.db csh.login gemrc jvm mke2fs.conf printcap rsyslog.d sysconfig
alternatives dbus-1 ghostscript jvm-commmon modprobe.d profile rwtab sysctl.conf
anacrontab default gnupg krb5.conf motd profile.d rwtab.d system-release
asound.conf depmod.d group kshrc motd.rpmsave protocols sasl2 system-release-cpe
at.deny dhcp group- ld.so.cache mtab racoon screenrc terminfo
audisp DIR_COLORS grub.conf ld.so.conf my.cnf rc securetty tmpfiles.d
audit DIR_COLORS.256color gshadow ld.so.conf.d nanorc rc0.d security udev
bash_completion.d DIR_COLORS.lightbgcolor gshadow- libaudit.conf NetworkManager rc1.d services update-motd.d
bashrc dracut.conf host.conf libreport networks rc2.d shadow vimrc
blkid dracut.conf.d hosts libuser.conf nsswitch.conf rc3.d shadow- virc
cfn dumpdates hosts.allow localtime ntp rc4.d shells wgetrc
chkconfig.d e2fsck.conf hosts.deny login.defs ntp.conf rc5.d skel X11
cloud elasticbeanstalk image-id logrotate.conf openldap rc6.d smrsh xdg
cron.d environment init logrotate.d opt rc.d ssh xinetd.d
cron.daily ethers init.d lvm pam.d rc.local ssl yum
cron.deny exports inittab magic passwd rc.sysinit statetab yum.conf
cron.hourly filesystems inputrc mail passwd- resolv.conf statetab.d yum.repos.d
cron.monthly fonts iproute2 mailcap pki rmt sudo.conf
Also tried this but nothing:
[etc]$ ps -ef | grep apache
ec2-user 3987 3543 0 02:53 pts/0 00:00:00 grep apache
What am I doing wrong here? My app was running fine the other day, but since some updates I pushed out I'm having this issue. I reverted them and it's still timing.
Elastic Beanstalk Rails stacks run nginx, not Apache. Try:
$ ps -ef | grep nginx
Also, your app directory should be under /var/app/current
Hope this helps.

Resources