import base64 #Decode xored = ‘KD4sPjsyNjE=’ plain = ”.join([chr(ord(c)^ord(‘_’)) for c in base64.b64decode(xored)]) #Encode enocoded = base64.b64encode(”.join([chr(ord(c)^ord(‘_’)) for c in plain])) ref: https://idmdepot.com/How_To/IBM_WebSphere_Application_Server_How_To.html
This article is for Docker Toolbox only. So when running docker toolbox, docker host boot2docker image running in VM on Virtual Box. When using docker toolbox, you will need to edit the start.sh BEFORE you start the docker command line prompt: USE %5C instead of “\” export HTTP_PROXY=”http://DOMAIN%5Cusername:password@proxy.proxydomain.com:8080″ export HTTPS_PROXY=”http://DOMAIN%5Cusername:password@proxy.proxydomain.com:8080″ and then you can start the docker…
addition note to the below comment that the default bridge network does support the DNS resolution. It confused me because the first few container was ran on a different configuration therefore cannot resolve each other. But when using docker compose, the containers are launched into default bridge network therefore they are able to talk to…