# How to resolve Pups exec errors during Discourse bootstrap

**URL:** <https://meta.discourse.org/t/how-to-resolve-pups-exec-errors-during-discourse-bootstrap/362619>\
**Category:** Support\
**Created:** [April 18, 2025, 12:38pm UTC](https://meta.discourse.org/t/how-to-resolve-pups-exec-errors-during-discourse-bootstrap/362619 "2025-04-18T12:38:46Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![Thomas\_Rother](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/thomas_rother/32/423597_2.png) [@Thomas\_Rother](https://meta.discourse.org/u/Thomas_Rother)\
**Post date:** [April 22, 2025, 4:27pm UTC](https://meta.discourse.org/t/how-to-resolve-pups-exec-errors-during-discourse-bootstrap/362619/16 "2025-04-22T16:27:21Z")

</div>

> [@RGJ](#):
>
> why isn’t it `alias: redis` ?

the file from /samples/web\_only.yml has

`# Use 'links' key to link containers together, aka use Docker --link flag. `  
`links: `  
` - link:`  
` name: data`  
` alias: data`

In my case the data container is a redis container

`CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS `  
` NAMES`  
`a27999b28a90 local_discourse/redis "/sbin/boot" 2 days ago Up 20 hours`

therefore `name: redis and alias: data`

According to the Docker docs this is a legacy feature, but its still useable, see [Legacy container links | Docker Docs](https://docs.docker.com/engine/network/links/)

I now think the better approach would be to create a standard “all in one” setup first (app.yml). And then sql dump the initial schema and data from the container into an external postgres machine. @Falco what do you think?

---

_[View the full topic](https://meta.discourse.org/t/how-to-resolve-pups-exec-errors-during-discourse-bootstrap/362619)._