diff --git a/Dockerfile-taloses b/Dockerfile-taloses
new file mode 100644
index 0000000..54c44fd
--- /dev/null
+++ b/Dockerfile-taloses
@@ -0,0 +1,31 @@
+FROM alpine:3.19.0
+
+RUN apk add --no-cache \
+        ca-certificates \
+        py3-kubernetes \
+        py3-yaml \
+        py3-jsonpatch \
+        curl \
+        wget \
+        openssl
+
+RUN wget https://github.com/siderolabs/talos/releases/download/v1.4.1/talosctl-linux-amd64 -O /usr/local/bin/talosctl-1.4.1 && \
+    chmod +x /usr/local/bin/talosctl-1.4.1
+RUN alias t41=/usr/local/bin/talosctl-1.4.1
+RUN wget https://github.com/siderolabs/talos/releases/download/v1.4.8/talosctl-linux-amd64 -O /usr/local/bin/talosctl-1.4.8 && \
+    chmod +x /usr/local/bin/talosctl-1.4.8
+RUN alias t48=/usr/local/bin/talosctl-1.4.8
+
+RUN wget https://github.com/siderolabs/talos/releases/download/v1.5.0/talosctl-linux-amd64 -O /usr/local/bin/talosctl-1.5.0 && \
+    chmod +x /usr/local/bin/talosctl-1.5.0
+RUN alias t50=/usr/local/bin/talosctl-1.5.0
+RUN wget https://github.com/siderolabs/talos/releases/download/v1.5.6/talosctl-linux-amd64 -O /usr/local/bin/talosctl-1.5.6 && \
+    chmod +x /usr/local/bin/talosctl-1.5.6
+RUN alias t56=/usr/local/bin/talosctl-1.5.6
+
+RUN wget https://github.com/siderolabs/talos/releases/download/v1.6.0/talosctl-linux-amd64 -O /usr/local/bin/talosctl-1.6.0 && \
+    chmod +x /usr/local/bin/talosctl-1.6.0
+RUN alias t60=/usr/local/bin/talosctl-1.6.0
+RUN wget https://github.com/siderolabs/talos/releases/download/v1.6.6/talosctl-linux-amd64 -O /usr/local/bin/talosctl-1.6.6 && \
+    chmod +x /usr/local/bin/talosctl-1.6.6
+RUN alias t66=/usr/local/bin/talosctl-1.6.6
diff --git a/README.md b/README.md
index b02d344..8539969 100644
--- a/README.md
+++ b/README.md
@@ -51,10 +51,20 @@ Check that kubectl resources are deployed as expected.
 
 ArgoCD can be accessed on the link after port forwarding 
 
-```kubectl port-forward svc/argocd-server -n argocd 8080:443 --kubeconfig=talos_outptu/kubeconfig``` 
+```kubectl port-forward svc/argocd-server -n argocd 8080:443 --kubeconfig=talos_output/kubeconfig``` 
 
 The credentials to access the ArgoCD GUI are present in the secret argocd-initial-admin-secret. These credentials need to be updated after the first login, and this would be a manual process. In a production environment the point is to never have to access the ArgoCD UI/CLI and instead have everything managed through in this case the https://github.com/eficode-academy/k8s-edge-gitops repo.
 
 You can retrieve the password using the command below:
 
-```kubectl --kubeconfig=talos_output/kubeconfig -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d; echo```
\ No newline at end of file
+```kubectl --kubeconfig=talos_output/kubeconfig -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d; echo```
+
+
+## Talos commands:
+`docker run -ti -v ${PWD}:/k8s-edge-infra -w /k8s-edge-infra taloss`
+`talosctl-1.4.1 -n 192.168.1.109 -e 192.168.1.109 --talosconfig talos_output/talosconfig dashboard`
+`talosctl-1.4.8 -n 192.168.1.109 -e 192.168.1.109 --talosconfig talos_output/talosconfig dashboard`
+
+## look at the application:
+
+[app](http://192.168.1.109/hello-python)
\ No newline at end of file