Two Key Challenges I’m Facing in My DevOps Journey

As I dive deeper into my DevOps journey, working with Jenkins, Docker, and Docker Compose, I’ve come across two recurring challenges that I feel are important to share. These are real hurdles I’m currently facing while setting up my projects.

1. Credentials Management in Jenkins with Docker Compose

While setting up a docker-compose.yml file to spin up my Node.js application and database container, I ran into a serious issue: where and how to store credentials securely.

Right now, I’m struggling with:

• Avoiding hardcoding usernames and passwords directly into the docker-compose.yml.

• Figuring out how Jenkins should pass these credentials safely during builds without exposing them.

This is one of the biggest blockers for me as I don’t want to compromise security while automating my pipeline.

2. Database Data Loss After Restarting Docker Compose

The second major issue I keep facing is related to my database container. Each time I run:

Copy

C

opy

and then restart my setup, my database comes up fresh, and all my previous data gets wiped out.

This makes it really difficult to maintain consistency during development, because every rebuild feels like starting from scratch.

Closing Thoughts

At this stage, these two problems—credentials management in Jenkins and database persistence in Docker Compose—are the biggest roadblocks in my DevOps journey.

In the next part, I’ll dive into possible solutions I’m exploring to tackle both issues