# OpenEMR 7.0.3 Patch 1 has been released **URL:** \ **Category:** News\ **Created:** [March 30, 2025, 8:04am UTC](https://community.open-emr.org/t/openemr-7-0-3-patch-1-has-been-released/25182 "2025-03-30T08:04:04Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![brady.miller](https://community.open-emr.org/user_avatar/community.open-emr.org/brady.miller/32/10178_2.png) [@brady.miller](https://community.open-emr.org/u/brady.miller)\ **Post date:** [March 30, 2025, 8:04am UTC](https://community.open-emr.org/t/openemr-7-0-3-patch-1-has-been-released/25182/1 "2025-03-30T08:04:04Z")
The 1st patch for OpenEMR 7.0.3 has been released: [https://www.open-emr.org/wiki/index.php/OpenEMR\_Patches](https://www.open-emr.org/wiki/index.php/OpenEMR_Patches) - [Click here to see CHANGELOG for detailed listing of new features and fixes.](https://github.com/openemr/openemr/blob/master/CHANGELOG.md#7031---2025-03-30) - Highlights include: - Date formatting fix in encounters. - Date formatting fixes in billing. - Security fixes. ---
**Author:** ![Even\_Pitch](https://community.open-emr.org/letter_avatar_proxy/v4/letter/e/0ea827/32.png) [@Even\_Pitch](https://community.open-emr.org/u/Even_Pitch)\ **Post date:** [March 30, 2025, 6:43pm UTC](https://community.open-emr.org/t/openemr-7-0-3-patch-1-has-been-released/25182/2 "2025-03-30T18:43:43Z")
Hello there. How does one go about updating their Docker Container of Open-EMR with patch 1 of version 7.0.3? I’m not finding any info on how to do it. Changing my Docker-Compose file of Open-EMR version “7.0.3” to “7.0.3.1” doesn’t work. ---
**Author:** ![stephenwaite](https://community.open-emr.org/user_avatar/community.open-emr.org/stephenwaite/32/15754_2.png) [@stephenwaite](https://community.open-emr.org/u/stephenwaite)\ **Post date:** [March 30, 2025, 6:52pm UTC](https://community.open-emr.org/t/openemr-7-0-3-patch-1-has-been-released/25182/3 "2025-03-30T18:52:03Z")
hi @Even_Pitch, is this an AWS cloud package? ---
**Author:** ![Even\_Pitch](https://community.open-emr.org/letter_avatar_proxy/v4/letter/e/0ea827/32.png) [@Even\_Pitch](https://community.open-emr.org/u/Even_Pitch)\ **Post date:** [March 30, 2025, 7:04pm UTC](https://community.open-emr.org/t/openemr-7-0-3-patch-1-has-been-released/25182/4 "2025-03-30T19:04:45Z")
Hi @stephenwaite, no, the Docker Container’s running on my Debian VM on my Macbook Pro. I was able to upgrade just fine from 7.0.2 after changing my Docker-Compose file version “7.0.2,” to “7.0.3.” I also changed the MariaDB version to, “11.6.2,” for the upgrade as well. ---
**Author:** ![stephenwaite](https://community.open-emr.org/user_avatar/community.open-emr.org/stephenwaite/32/15754_2.png) [@stephenwaite](https://community.open-emr.org/u/stephenwaite)\ **Post date:** [March 30, 2025, 7:14pm UTC](https://community.open-emr.org/t/openemr-7-0-3-patch-1-has-been-released/25182/5 "2025-03-30T19:14:59Z")
hi @Even_Pitch, wouldn’t mess with the docker compose file since there are dependencies that might affect the application. Instead you copy in the patch 1 zip into the docker and unzip from the web root. ```auto Linux 1. Move the patch file to the openemr web directory, then type 'unzip 7-0-3-Patch-1.zip', and confirm ok to copy over files. 2. Open web browser and go to http://your_server_name_or_ip/openemr/sql_patch.php (this script will run automatically and patch the database) (if you are using the Multisite Module, then skip step 2 and follow these instructions) 3. Delete the sql_patch.php file from the openemr web directory ``` ---
**Author:** ![Even\_Pitch](https://community.open-emr.org/letter_avatar_proxy/v4/letter/e/0ea827/32.png) [@Even\_Pitch](https://community.open-emr.org/u/Even_Pitch)\ **Post date:** [March 31, 2025, 1:26am UTC](https://community.open-emr.org/t/openemr-7-0-3-patch-1-has-been-released/25182/6 "2025-03-31T01:26:22Z")
Ok @stephenwaite I’ve been searching online to try and answer my additional questions and having a hard time. I’m still pretty new at this; hence, why I’m keeping all this locally on my laptop. Anyway, the Openemr web directory: is this a folder in the Docker container? How do I find it? Looking through a write up on restoring OpenEMR Container from a backup ([https://benmarte.com/blog/openemr-backup-restore](https://benmarte.com/blog/openemr-backup-restore)), they showed how to copy the .tar.gz backup file into the container and extract it. Is this similar to what you’re talking about in step 1? ---
**Author:** ![brady.miller](https://community.open-emr.org/user_avatar/community.open-emr.org/brady.miller/32/10178_2.png) [@brady.miller](https://community.open-emr.org/u/brady.miller)\ **Post date:** [March 31, 2025, 5:24am UTC](https://community.open-emr.org/t/openemr-7-0-3-patch-1-has-been-released/25182/7 "2025-03-31T05:24:14Z")
hi @Even_Pitch , To do this in dockers, check out these instructions: [openemr-devops/packages/lightsail at master · openemr/openemr-devops · GitHub](https://github.com/openemr/openemr-devops/tree/master/packages/lightsail#applying-upgrades-and-security-patches) (don’t do the `/etc/cron.daily/duplicity-backups` since this is not an aws docker) Also to clarify, the automatic upgrades (where change the docker-compose to a new version) is only supported for the standard releases. The patches require the manual approach above. ---
**Author:** ![Even\_Pitch](https://community.open-emr.org/letter_avatar_proxy/v4/letter/e/0ea827/32.png) [@Even\_Pitch](https://community.open-emr.org/u/Even_Pitch)\ **Post date:** [March 31, 2025, 7:12pm UTC](https://community.open-emr.org/t/openemr-7-0-3-patch-1-has-been-released/25182/8 "2025-03-31T19:12:18Z")
Thank you so much @brady.miller, I got it to work. It took some tweaking though, as the command, "OE\_INSTANCE=$(docker ps | grep \_openemr | cut -f 1 -d " “),” didn’t insert the docker ID into the commands that came after automatically. But, all I had to do was cut and paste the container ID right after wherever, “OE\_INSTANCE” was listed in the script you had me use and I was able to complete the patching process. I sincerely appreciate your help, as well as the help from @stephenwaite. Thank you both for your time. - Matt