Re: [CentOS] Docker on Centos 7

2019-01-06 Thread H
On 01/05/2019 06:44 AM, Daniel Walsh wrote:
> On 1/4/19 9:50 PM, H wrote:
>> On 01/04/2019 09:16 PM, H wrote:
>>> On 01/04/2019 08:27 AM, Daniel Walsh wrote:
 On 1/4/19 8:22 AM, Daniel Walsh wrote:
> On 1/3/19 10:19 PM, H wrote:
>> I recently updated docker to version 18.09 and I seem to have lost the 
>> container id in the command prompt when I exec into a running container, 
>> a very useful feature in the previous version I was running. I have not 
>> found any information in the Docker General Forum.
>>
>> Has anyone else seen this?
>>
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
> Most likely you had hostname set in the bash prompt.  By default
> containers run with the hostname=containerid.
>
>
> # podman run -v /usr/bin/hostname:/usr/bin/hostname -ti fedora hostname
> 3ac978bc84be
>
>
> |PS1="\h$ " Should give you what you want # podman run -ti fedora sh
> sh-4.4# PS1="\h# " 9007d2f699fb# exit # But I think this would need to
> be added to the .bashrc or .bash_profile inside of the container image
> you are running. |
 Also if you execute sh -l instead of sh, it will do what you want.


 podman run -ti fedora sh -l
 [root@81674750cd2a /]#
 [root@81674750cd2a /]# exit


 ___
 CentOS mailing list
 CentOS@centos.org
 https://lists.centos.org/mailman/listinfo/centos
>>> But when/why did this change? Is there a change in docker that resulted in 
>>> this? Or was it the latest update to CentOS 7?
>>>
>>> I have not made any changes otherwise.
>>>
>>> ___
>>> CentOS mailing list
>>> CentOS@centos.org
>>> https://lists.centos.org/mailman/listinfo/centos
>> I should have added that I do not use podman to run my docker containers.
>>
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
> I don't think this is a change in either podman or docker.  Their might
> have been a change in the container image that you were running and
> seeing this behavior.  Perhaps the centos image was setup to do this
> automatically.
>
> BTW Podman and Docker run the same containers,  IE Any container image
> stored at any container registry,  (Docker.io, Quay.io,
> registry.centos.org ...)
>
>
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos

I just realized that for a couple of my containers the prompt does show the 
container id as before, however, one of my containers where I installed the 
most recent version of python from SCL, it does not. In all cases the 
containers use the CentOS 7 image, the rest I build myself. I have to figure 
out why the python container behaves differently.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] how to set proxy systemwide (wget and docker)

2019-01-06 Thread Simon Matter via CentOS
> Hallo,
> what is the right way to set a proxy systemwide using centos 7?
> I need this for wget and docker.
> My first idea was /etc/environment but allthough the proxy is set wget and
> docker don‘ t connect to their target-systems.

I have this in /etc/profile.d/proxy-config.sh:
-%<-
PROXYHOST="proxy"
PROXYPORT="8080"

for CFGFILE in /etc/sysconfig/proxy-config ${HOME}/.proxy-config; do
  [ -s $CFGFILE ] && . $CFGFILE
done

export http_proxy="http://${PROXYHOST}:${PROXYPORT}";
export HTTP_PROXY="http://${PROXYHOST}:${PROXYPORT}";
export https_proxy="http://${PROXYHOST}:${PROXYPORT}";
export HTTPS_PROXY="http://${PROXYHOST}:${PROXYPORT}";
export ftp_proxy="http://${PROXYHOST}:${PROXYPORT}";
export FTP_PROXY="http://${PROXYHOST}:${PROXYPORT}";
export all_proxy="http://${PROXYHOST}:${PROXYPORT}";
export ALL_PROXY="http://${PROXYHOST}:${PROXYPORT}";
export no_proxy="localhost,$(hostname -s),$(hostname -f),$(hostname
-d),127.0.0.1"
export NO_PROXY="localhost,$(hostname -s),$(hostname -f),$(hostname
-d),127.0.0.1"
export RSYNC_PROXY="${PROXYHOST}:${PROXYPORT}"

unset PROXYHOST PROXYPORT CFGFILE
-%<-

Regards,
Simon

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] how to set proxy systemwide (wget and docker)

2019-01-06 Thread Ralf Prengel


Zitat von Simon Matter via CentOS :


Hallo,
what is the right way to set a proxy systemwide using centos 7?
I need this for wget and docker.
My first idea was /etc/environment but allthough the proxy is set wget and
docker don‘ t connect to their target-systems.


I have this in /etc/profile.d/proxy-config.sh:



Hallo,
works perfect for wget.
Docker fails
[root@srvdockerndxx tmp]# docker run --rm --privileged -v  
/var/run/docker.sock:/var/run/docker.sock -v  
/var/lib/rancher:/var/lib/rancher rancher/agent:v1.2.10  
http://192.168.x.y/v1/scripts/811F51C097F763ABA2E5:154621440:Nzpsvk8sbaKXle3QYotSNzUFk

Unable to find image 'rancher/agent:v1.2.10' locally
Trying to pull repository docker.io/rancher/agent ...
/usr/bin/docker-current: Get https://registry-1.docker.io/v2/:  
net/http: request canceled while waiting for connection  
(Client.Timeout exceeded while awaiting headers).

See '/usr/bin/docker-current run --help'.
[root@srvdockerndxx tmp]#
Seems as if docker needs more or other proxy-configurations.

Ralf


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] how to set proxy systemwide (wget and docker)

2019-01-06 Thread Ralf Prengel


Zitat von Simon Matter via CentOS :


Hallo,
what is the right way to set a proxy systemwide using centos 7?
I need this for wget and docker.
My first idea was /etc/environment but allthough the proxy is set wget and
docker don‘ t connect to their target-systems.



Hallo,
https://forums.docker.com/t/docker-installing-docker-behind-a-proxy-on-centos-7-error-while-pulling-image/26015
solves my problem.

Ralf



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] Upgrade CentOS 7.4 to 7.5 and don't want to upgrade it to 7.6

2019-01-06 Thread Kaushal Shriyan
Hi,

Is there a way to upgrade from Centos Linux release 7.4.1708 (Core) to
Centos Linux release 7.5.1804 (Core) and not up to CentOS Linux release
7.6.1810 (Core) as the product does not support the latest CentOS Linux
release 7.6.1810 (Core) version as of now. It is still a work in progress.
Any help will be highly appreciable. I look forward to hearing from you.

Thanks in Advance.

Best Regards,

Kaushal
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos