Images not visible after docker-compose down && docker-compose up

I have deployed twenty using docker on an ec2 instance with storage configured in S3. When I upload images in Files, I can see them when I log out and log back in. I can even see them in the S3 bucket. However, when I make local changes and want to update my deployed version, I build the docker image, update docker-compose yml file & then I do docker-compose down && docker-compose up. I usually get sync error so I run docker exec -it twenty-server yarn command:prod workspace:sync-metadata When I log back in, I only see the image icon instead of the image . Has anyone ever faced this? I'd appreciate any help!
No description
3 Replies
Prastoin
Prastoin7d ago
Hello @Amiteshwar, locals update ( custom objects etc ) are not persisted to the build Only the source code - are you sure you consume your custom built twenty image ? - what sync metadata error are you getting exactly ? Just because I'm curious, what does your custom build implements ?
Amiteshwar
AmiteshwarOP6d ago
@prastoin Yes, this image was attached to a record in a custom object. But, the image is hosted in an S3 bucket. So, shouldn't it persist? Q1: "are you sure you consume your custom built twenty image ?" --> Yes, I update my docker-compose.yml with the new image for server & worker. Q2: "what sync metadata error are you getting exactly ?" --> I get this error in the server when I try to login after updating: "Metadata version not found for workspace 16f21d51-6f79-4625-80e0-7156d0dcf29" I don't always get this error. In the cases when I don't get the error, the images persist. But, it's rare. Q3: "what does your custom build implements ?" --> Just the updated code. The Dockerfile is same but I updated entrypoint.sh @prastoin curious, do you also get this error when you try to login after you do docker compose down && docker compose up? "Metadata version not found for workspace 16f21d51-6f79-4625-80e0-7156d0dcf29"
Prastoin
Prastoin6d ago
Hello @Amiteshwar this is a cache issue try flushing it you cache:flush command in server container Please double check command on phone right now

Did you find this page helpful?