All rapyuta.io docs are open source. See something that's wrong or unclear? Submit a pull request.
Make a contributionrapyuta.io uses your docker pull secret during Development Builds as well as Package Deployment. When you want to use a docker image from your private (docker) registry, you grant rapyuta.io access to your private registry by creating a docker secret.
The two types of docker pull secrets that you can create are:
To create a docker secret for a private docker registry, do the following:
On the left navigation bar, click Account > Secrets.
Click ADD NEW SECRET.
In the Name field, enter a name for the docker secret.
The name should be less than 253 characters. It must consist of lower case alphanumeric characters and hyphen(-). It must begin and end with an alphanumeric character.
You can select the executable type as one of the following.
a. Enter your Username, specify your password, and Email ID in the respective fields.
b. Additionally, if your executable type is Private Registry, provide the registry URL in the Registry Url field.
Click SUBMIT. The docker secret for the rapyuta.io platform is created.
To edit a secret, click the edit icon under Action.
To access private Docker registries:
rio secret create -t docker <secret_name>
Specify the username, password, email id, and import docker.
docker username: <user_name>
docker password: <password>
docker email: <email>
To automatically import Docker credentials from the environment:
rio secret import docker
When you create a docker pull secret for a private registry, rapyuta.io stores your docker credentials (that is, username and password) in base64-encoded format. This encoded data is the *_ authorization token_* which gives access to rapyuta.io to pull private docker images while deploying a package.
To determine your docker credentials for a private registry, run the following instructions in sequence on the system you have logged in to docker:
config.json file. To display this file, run the following command:cat ~/.docker/config.json
A sample config.json file will look like:
{
"auths":{
"https://index.docker.io/v1/":{
"auth":"c3r...ze2"
}
}
}
The value of auth entry is base64-encoded data called *_ authorization token_*. If you use a docker credentials store, you will instead see credsStore entry with the name of the store as value. For example, a sample config.json file with credsStore entry would look like:
{
"auths":{
"https://index.docker.io/v1/":{}
},
"credsStore": "osxkeychain"
}
You can find out the authorization token from the respective credsStore entry’s value. In this case, use osxkeychain value to figure out the authorization token.
To convert *_ authorization token_* to a readable format, execute the command:
echo "c3r...ze2" | base64 -d
The output consists of two parts separated by a colon : as shown below
janedoe:xxxxxxxxxx
The part to the left of : is your docker username, while the one on the right is your password.
If you encounter the following deployment error, Ensure the docker username and password in a secret are correct.
DEP_E153 (Could not pull either the docker image or the built package artifact for the component on the cloud)