Korean Shredded Beef Tacos - Gluten Free Dairy Free Version - Dump and Go Dinner
Korean Shredded Beef Tacos - Gluten Free Dairy Free Version - Dump and Go Dinner
Savory, sweet and with just enough spice our Gluten Free Dairy Free Korean Shredded Beef Tacos cook up with little effort thanks to the slow cooker! These little corn tortillas filled with tender meat set the tone for a delicious and simple fusion-style meal.
Ingredients
- 3 pounds Beef Roast
- ¼ cups Honey
- ⅓ cups Soy Sauce, Gluten Free
- 10 teaspoons mince Garlic, Cloves
- 1 cup dice Onion
- 2 tablespoons peel and mince Ginger, Fresh
- 2 tablespoons Rice Vinegar
- 1 tablespoon Sesame Oil
- 1 tablespoon seed and dice Jalapeño
- 24 individual Corn Tortillas
Containers
Supplies
Cooking Instructions
Freeze For Later Cooking Day Directions
These directions help you cook or prepare this meal PRIOR to being frozen for serving later (see Serving Day Directions when you are ready to prepare it to eat).
Why would I want to freeze this?
- Mix all ingredients together (except tortillas).
- 3944117 Upgrade to a paid membership 81150 to unlock all instructions 28702
- 8791691 Upgrade to a paid membership 722 to unlock all instructions 34568
Upgrade to a paid membership to unlock all recipe instructions
Make From Frozen Serving Day Directions
These directions help you cook or reheat this meal AFTER it's been frozen for when you are ready to eat it.
- Thaw: In fridge
- 5861015 Upgrade to a paid membership 43809 to unlock all instructions 1821
- 3369602 Upgrade to a paid membership 24248 to unlock all instructions 40960
Upgrade to a paid membership to unlock all recipe instructions
Make It Now Cooking Directions
These directions are for cooking this recipe to serve immediately and NOT to freeze for later.
- Mix all ingredients together (except tortillas).
- Cook in slow cooker on low for 8-10 hours until fork tender.
- Shred and serve on corn tortillas.
Nutrition Facts
- Servings Per Recipe
- 12 Servings
- Serving Size
- 2 tacos Amount Per Serving
- Calories
- 424
- Total Fat
- 10g
- Saturated Fat
- 2g
- Trans Fat
- 0g
- Cholesterol
- 74mg
- Sodium
- 491mg
- Total Carbohydrates
- 55g
- Fiber
- 0g
- Sugar
- 11g
- Protein
- 30g
- WW Freestyle
- 12
23 Comments
Join the discussionLOVED THIS! I cooked just as recipe says and served it with coleslaw, avocados and fresh mangos! So good…ate it for dinner, breakfast and lunch!!
I was just curious how it’s recommended we eat the meat? Soft corn taco shells? I appreciate Terri’s comment about what she ate with it! I just froze this meal a few days ago and it smelled FABULOUS, I can’t wait to cook it!!!!
Hi! I have used corn tortillas for serving, but you could serve in taco shells, over baked sweet potatoes, on quinoa or rice or on wide rice noodles. Other options are as a hot sandwich filling in gf moo shu wrappers (http://angelaskitchen.com/2008…, gf french bread (http://angelaskitchen.com/2007… or on toasted gf hamburger buns (http://angelaskitchen.com/2012…. I also sautéed some bok choy and kale, heated some of the meat (left over from dinner) and had that for breakfast with a peach one morning. Yum! Hope those ideas help. 🙂
sorry— I do see here is says tortillas. (Though not on my printed recipe)… any other suggestions, though? THANKS!
I made extra sauce and put this on rice noodles with kimchi and sautéed baby bok choy. So good!
Oh that sounds YUMMY!
I never thought I would see “Korean” and “Tacos” in the same recipe title. But the marinade does sound delicious!
Not a fan of jalapenos. Never have been. Hubby likes them so he can serve his as a side but could you do a can of hatch green chiles instead? Or just leave them out?
I think green chiles would be good!
I only put one jalapeño and could barley taste it…but over all it was very good and I will be making it again!
Thanks for the feedback, JanJan! I like my spicy foods to be relatively intense in heat, so if you fall a little more in that camp you could use a Serrano pepper to give it more kick. It’s a couple notches above the Jalapeño heat wise on the Scoville Scale http://foodreference.about.com….
I assume the slow cooker is supposed to be on LOW for this recipe? It doesn’t specify.
You assume correctly, Liz! Great catch- I’ll pass the change along to our menu team!
Since this recipe is on one of your paleo freezer menus, you should probably have a disclaimer that the soy sauce and corn tortillas are NOT paleo friendly and should be substituted.
Dusty, we’re aware of that – this recipe is not tagged as Paleo and if it is on a Paleo menu we’d like to correct that. Which menu are you referencing? Thank you!
It is on the Spring Paleo Freezer Menu Vol. 1.
https://onceamonthmeals.com/menus/spring-paleo-freezer-menu-vol-1/
Thank you! I will pass this along to our MenuBuilder team.
Can this be pressure cooked instead of crock pot? If so how long would I cook instead?
You absolutely can. Here is a helpful post to help you determine cooking time. We’d love to hear how it turns out! Enjoy!
It calls for 3 freezer bags. How do you split up, and why? Then do you recombine all when cooking? Also, do you defrost first? (That last part about defrosting is a question I have on all freezer to crockpot recipes, actually.)
Since this recipe is for 12 servings you might like to put 4 servings in each bag. See step 2 on the second set of directions. You can recombine if you like but unless you’re seving 12 people it’s like not necessary. Yes, you will want to thaw in the fridge. In regard to your general question about thawing crockpot freezer meals it depends on the recipe. The documents our members receive include thaw instructions. If you have more questions, we’d love to chat with you in the bottom right-hand corner.
This is still in the Paleo Spring Menu, despite being mentioned 6 months ago as not compliant. It’s really tough to use your site if your recipes are categorized correctly, and aren’t fixed even 6 months after being notified of the error.
Erica,
You are correct, that is disappointing. I am not sure how that recipe got on that menu in the first place as it is not tagged as a Paleo recipe in our database. It should not have taken us 6 months to make the change and we are sorry that it did. We are working for better processes to ensure this type of mistake doesn’t continue to happen.