-
So for the last 2 days I have been trying to get this to work in Docker or anything in that matter. The install seems to work fine, but when I get to the test part it fails. My Docker environment is a little different, but everything is stored in a Docker folder and all of my binds are kept in folder call appdata within the docker folder. I have watched about a half dozen or so videos, to include Smallsteps, but mainly been following your instructions here. Steps I've taken
After following all the steps I get confirmation everything worked
As you can see it's very basic just to get it up and running. I'm using Portainer to view the logs and VSCode to modify any the files. But when I try to test with I have even tried using my DNS name Also shortly after that Portainer shows the container as Unhealthy. What am I doing wrong here, I followed the instructions to a I'm on Ubuntu 22.04.3 I believe or which ever is the latest. Docker and Docker Compose are all the latest versions. This was a fresh install and I disabled the firewall. Any help you can provide me would be greatly appreciated. Thank you in advance. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
So I think I have it figured out. While that bootloader is supposed to put the certificate in the trusted store, it didn't. After copying the certificate to the location.
So the full Compose file looks like this:
I will try this on my original device and if I can get to work I will close this out. |
Beta Was this translation helpful? Give feedback.
So I think I have it figured out. While that bootloader is supposed to put the certificate in the trusted store, it didn't. After copying the certificate to the location.
sudo cp appdata/step/certs/root_ca.crt /usr/local/share/ca-certificates/
Then update the certificates
sudo update-ca-certificates
.I also had to add this to the end of my compose file which seem to do the trick from my main device.
So the full Compose file looks like this: